Hello HubSpot Community,
My name is Daniel Spillers. I am a CRM Developer that works with Dynamics 365, PowerApps, Power Automate Flows. Currently, we are transitioning from Salesforce for our Leads generation into HubSpot. Very exciting change!
I’ve been looking at the Workflows functionality, and it seem pretty straightforward. However, I need to connect my data again to Dynamics 365 using Power Automate. I would use the built in integration, but we have to be more granular about the accounts we pull into our DataVerse environment as we have a blend of accounts and only certain ones need to be pulled into my end of the program. I need to create a workflow with a webhook. The webhook part works no problem. I am able to return data in my initial testing. However, I need HubSpot to run that workflow if anything in our Accounts (Company) change. Unless I am blind, I do not see that I am capable of actually just making hubspot run the workflow based on any anychange in the record. So, I tried the last modifed date field. The options available don’t see to allow me to use a formula in order to run. Also, Im afraid to see if I just set the trigger to “After today” because I don’t know the exact behavior of doing so. Help me out community! What is the easiest way to resolve this use case? Salesforce has triggers in Power Automate which made it easy to run when using connectors. HubSpot has Actionsin Power Automate, which are not the same thing. I guess I could Batch them, but I wanted them to be individual runs. Is it possible? 
Thanks all.
“is known” in the filter options is generally considered the same as “has changed” in the majority of cases.
When using the property filter is known for re-enrollment, in addition to meeting the criteria listed above, records can re-enroll in two ways:
- The property gains a value after not previously having one.
- The property is updated from one value to another. For example, a contact's lifecycle stage changing from Lead to Subscriber would qualify for Lifecycle stage is known. Each time this contact's lifecycle stage is updated, they would re-enroll in the workflow, provided the contact also meets the workflow's initial enrollment triggers.
So you can create a workflow either with an event change or a filter criteria.
Please note that if the trigger happens often, Hubspot will ignore subsequent enrollment on the object until the object clears the workflow.
Thank you, MichaelMa. Great to know and thanks for sharing documentation on this. You erally helped me out
Hi,
According to the information that I gathered from MD365 Integration team, might suggest some ideas.
If you need a HubSpot workflow to start when an Account changes, webhooks are likely your best choice. Webhooks let HubSpot send data to a Power Automate flow when an account is updated. This gives you control over which updates start your flow. Once the webhook is sent, Power Automate gets the newest data, and you can do what you need. If webhooks seem hard, you could try HubSpot’s Last Modified Date thing. It’s not as accurate as a webhook, but you can make the workflow start when the “Last Modified Date” is updated, or if it’s updated within the last day. It’s easier, but it might not be instant if a lot of edits are happening. In Power Automate, your flow can handle each update one at a time, running each time the webhook fires. This means updates aren’t grouped.
So, HubSpot webhooks are probably better since they offer more control over when your workflow starts, based on Account edits.
Ivan Farafonov