Zapier vs Make… what’s been your experience?
I’ve been building out more automations around Jobber lately and ran into something interesting. A lot of setups I see are using Zapier, but once workflows get more complex, the cost starts climbing ...
Forum Discussion
Agree with you from a UI perspective DrewR. The visual layout of Make helps me understand the workflow better. The reality is that both tools work. The real constraint for Jobber users isn't which platform you choose; it's what data is actually available to build on.
Zapier's native Jobber connector covers the basics well enough for simple workflows. Where it tends to fall short is when you need to trigger on specific Jobber events or pass custom field data downstream. That's when people hit the wall and assume the platform is the problem.
There are tools in the Jobber app marketplace that extend what's available to build on. For Zapier users, that means access to 50+ triggers and actions — including custom field data and events the native connector doesn't expose. For Make users, it means webhook support for Jobber events, which you can point directly at a Make scenario for real-time triggers rather than relying on polling.
In both cases the platform isn't the bottleneck, it's whether you have the right Jobber data to work with in the first place.