APIs & Integrations

EPBrivity
Participant

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

Based on what I've seen with the "Updated Deal Stage" trigger, it only supports a single pipeline. Is there a way to indicate mutliple pipelines? I would rather set up a single zap for all pipelines to manage rather than set up 6 separate zaps that require more edits.

5 Replies 5
EPBrivity
Participant

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

@danmoyle @Jaycee_Lewis I ended up finding a different trigger altogether that I believe fits my needs: "New Deal Property Change", which allows the user to choose a specified deal property to monitor. In this case I chose Deal information: Deal Stage, which triggers any time a stage is updated on any deal in our instance. From there I am running a Zapier Filter step to only continue if the incoming trigger includes the my desired Deal Stages. This has enabled me to monitor multiple pipelines at once (yippee!). Thanks for your thoughts!

danmoyle
Most Valuable Member | Elite Partner
Most Valuable Member | Elite Partner

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

That's fantastic. Thank you for thinking of us to update, @EPBrivity ! 

 

Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!


Dan Moyle

HubSpot Advisor

LearningOps | Impulse Creative

emailAddress
dan@impulsecreative.com
website
https://impulsecreative.com/
Jaycee_Lewis
Community Manager
Community Manager

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

Hey, @EPBrivity! Thanks for creating the post and allowing us to brainstorm alongside you 🙌  Have a great rest of your week! — Jaycee

linkedin

Jaycee Lewis

Developer Community Manager

Community | HubSpot

danmoyle
Most Valuable Member | Elite Partner
Most Valuable Member | Elite Partner

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

Hi @EPBrivity. I'm with @Jaycee_Lewis on this - I think they're right that it would have to be multiple Zaps from what I can tell. In a HubSpot workflow, it doesn't have to be one pipeline. But for Zapier, it seems to. I'm not sure where that limitation is from, if it's the zaps or on the HubSpot side. 

 

But if you have operations hub, you can do all the webhook actions you want, including custom-coded actions, which could eliminate zaps altogether potentially. 

 

Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!


Dan Moyle

HubSpot Advisor

LearningOps | Impulse Creative

emailAddress
dan@impulsecreative.com
website
https://impulsecreative.com/
Jaycee_Lewis
Community Manager
Community Manager

Zap Trigger - Updated Deal Stage: Support for Multiple Pipelines?

Hi, @EPBrivity 👋 Thanks for reaching out! 

 

The short answer — you're correct that if you need to automate based on changes across multiple pipelines, you would need to create separate zaps for each pipeline.

 

I'd like to invite some of our experienced community members to share their experiences or strategies — hey @danmoyle @ChrisoKlepke @Bryantworks do you have any Zapier + HubSpot wisdom you can share with @EPBrivity?

 

Thank you! — Jaycee

linkedin

Jaycee Lewis

Developer Community Manager

Community | HubSpot