Support engagement_communication model

[zmandell]

Is there an existing feature request for this?

• [X] I have searched the existing issues

Describe the Feature

the Fivetran connector now includes the engagement_communication table

Describe alternatives you've considered

I think I can fork the repo and work off my own updates

Are you interested in contributing this feature?

• [X] Yes.
• [ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
• [ ] No.

Anything else?

No response

[fivetran-avinash]

Hi @zmandell ! Thanks for raising this feature request.

Before moving forward, I want to properly scope out what the request is here that will provide you the best possible value.

1. Do you want to simply add the engagement_communication model to dbt_hubspot_source where we add the table to the source package, then have that table available to fork for your own purposes?
2. Did you want the engagement communication data integrated into the end models in the dbt_hubspot transformation package, where we add another engagement event end model (like the ones you see here) and then add engagement_communication model logic to existing hubspot models?

The first ask is relatively straightforward, and you should be able to open a PR on the source package that we can review and try and help you ship live. The second ask is a bit more complex and we'd have to do some additional review to prioritize it. But if you're aligned with (1) we can definitely try and get this feature out and into the dbt_hubspot_source package as soon as you have a PR out!

Let us know your thoughts or if you have any questions here!