- Add filters to Zap to automate only when a condition is satisfied in the triggering platform. This will limit the number of tasks being executed via Zapier. You can learn how to add condition to a Zap here.
This setting can come in very handy when you want to create prospects only when a stage is reached or when a field is updated. For example, you can set a condition that prospect should only be created in Upscale when the source is LinkedIn or prospect should only be updated into CRM if its stage is Replied Interested.
- Branch Zaps into paths to configure complex sales flows between apps. This can help you in achieving if else condition in Zapier. You can learn how to create Zaps with conditional path here.
- When you use Zapier with your team, each user will have to setup their Zap configuration individually. This may increase your number of Zaps being used for a single configuration. If you wish to cut down on your Zap usage, you can assign the records to a single user in your triggering app and then re-assign the records to other users when it lands in other platform.
