topic Re: Multiple triggers for deal properties change in APIs & Integrations

Multiple triggers for deal properties change

ASalme — Tue, 24 Jun 2025 10:21:33 GMT

Hi, I'm trying to set up a Workflow where a POST is sent whenever any of a group of deal properties changes.

What I’d like to do is have multiple triggers in the same workflow, each pointing to different webhooks—so when property A changes, it hits webhook A, when property B changes, it hits webhook B, and so on.

Having a single trigger with all the properties as conditions, pointing to the same webhook, will send either all the properties or manually filter what to send. That’s not ideal, I really just want to send only the property that actually changed. Also the option to have a workflow per trigger is not possible, cause my fields can increase or decrease over time so creating or removing workflows not sure if is the best option.

Anyone know if that kind of setup is possible? Or any workarounds you’ve used?

Thanks!

Re: Multiple triggers for deal properties change

ASalme — Tue, 24 Jun 2025 11:13:17 GMT

Is an app with webhooks suscriptions a better option than a workflow?

Re: Multiple triggers for deal properties change

Jaycee_Lewis — Tue, 24 Jun 2025 17:35:23 GMT

Hey, @ASalme 👋 I think creating an App and using Webhooks will be your best bet. I think we can work out something using If/Then branches, but it comes with limitations. Using Webhooks will give you the granularity you need.

Workflow limitations:

No Dynamic Data — can't send only the specific property that changed
Sequential Logic — only the first matching if/then branch will run, not all of them
Lacks Scalability — requires manually adding a new branch for every new property
No Trigger Awareness — the workflow can't identify which property change triggered it

If you are only needing this for a single HubSpot portal, you can simplify things a little by using a Private App for your Webhooks (versus a Public App which can be installed into multiple portals) — Webhooks and Private Apps.

Private App Advantages:

Precise Data — the webhook payload tells you exactly which property changed and its new value
Highly Scalable — track new properties without changing your setup in HubSpot
Powerful & Centralized — enables complex logic and consolidates your code in one external application
Real-Time Trigger — our system is notified instantly when a change occurs

You could set up a Developer account and create a Developer test accounts to test with if you want to protect your production portal.

Have fun testing! — Jaycee

Re: Multiple triggers for deal properties change

GiantFocal — Fri, 27 Jun 2025 14:52:02 GMT

Hi @ASalme,

Right now, HubSpot workflows don’t support multiple property-specific triggers within a single process, and they can’t automatically send only the property that has changed. A workaround is to create an external app using a Private App and webhooks, which listens for property changes.

With this setup, you only need one integration, and your app can process the incoming webhook, pinpoint which property was updated, and direct the data to the right destination. This method is flexible and can grow with your needs without needing constant updates in HubSpot as your list of properties evolves.

If you’re not ready to build an app, you could use If/Then branches in a workflow, but this method is less scalable and only triggers the first matching condition.

Re: Multiple triggers for deal properties change

ASalme — Fri, 27 Jun 2025 15:25:45 GMT

Hi @GiantFocal, Yes, I went for that solution, which is quite simple to implement, works perfectly, and is exactly what I needed.

Thank you!