Zapier
Overviewโ
Zapier is a platform which allows you to build automation workflows (Zaps) between a wide range of third-party applications (8,500+), including JobStaq.
Some example use cases include:
- Syncing customers created in JobStaq to a sales CRM or marketing automation platform
- Creating jobs from emails received to an inbox
- Creating events in JobStaq when created in a third-party scheduling software
Zapier offers a free plan which allows the creation of 2 step (trigger + action) Zaps with a limit of 100 tasks per month, and paid plans start at ยฃ15/month for 750 tasks.
JobStaq also offers an integration with Make.com, an alternative automation platform to Zapier, which in most cases works out cheaper (although has a smaller library of supported apps).
Featuresโ
JobStaq provides support for:
- Triggers, which instantly starts a Zap when a record is created, updated, or deleted (configurable) in JobStaq
- Actions, which allow you to create records in JobStaq from a Zap
- Searches, which allow you to locate records in JobStaq from a Zap
At present, the integration supports the following record types:
- Customers
- Properties
- Jobs
- Employees
- Events
- Communications
Setup Processโ
- Sign up for a Zapier account on Zapier's website, https://zapier.com/sign-up.
- Click here for the invite link to add the private JobStaq app to your Zapier account.
- Generate an API key in the JobStaq web interface, by navigating to Company Settings > Developer > API Keys, or clicking here.
- Create a new Zap for the first automation you wish to build with JobStaq. When adding the first JobStaq step to the Zap, you'll be prompted to connect an account. Enter the API key from the step above here, and click the continue button to authenticate Zapier with your JobStaq account.
Limitationsโ
The integration is still in the early stages, and presently triggers and actions only include data which is directly part of the record, without any related records. For example, a job created trigger will include the job details, and customer ID, however, not the customer details themselves. Until support is added for this data in trigger payloads, you'll need to use the search functionality to locate related records if you need their details.