Robust Automation Solution
Use Cases and Deployment Scope
We use Zapier to automate workflows related to customer data across different platforms. It enables us to capture user data from various applications and centralize the data for stakeholders who may not have access to the source app. The goal being to eventually build a central customer health score, but we're starting small with individual elements.
Pros
- No code Zap builder - You don't have to understand APIs to retrieve and send data where you need it
- Suggested data - within the builder, Zapier recommend data elements that would complement the triggers/actions you have.
- Tooltips - Zapier has great tooltips and explanations for everything (triggers, actions, specific data fields) that really help you understand what you're building and if will help you achieve your goal
- Configure/Testing process - each Zap step has a built in testing process to ensure the Zap will work before you finish the whole thing. You don't have to worry about building the whole flow only to realize you missed a critical step that completely messes up the whole thing
Cons
- Although the Zap testing is built into each step, I find it inconvenient to test individual actions once the Zap is published. If I know the issue is in action 8 or 15 and need to test the flow with a new trigger record, I have to start at the top with a new record and manually all the steps up to that point. Maybe it already exists, but I would love to select a new test record and automatically perform selected steps all at once, (i.e. actions 1-8 in one click).
Return on Investment
- With one Zap I easily save an hour of work each day, enabling me to take of more nuanced challenges that don't have a regular flow. The more successful Zaps you build, the more potential savings. It's amazing to think about.
Usability
Alternatives Considered
Microsoft Power Automate
