Make.com

Supported plans:

❌Bronze

❌Silver

✅Gold

Overview

Make.com is a platform which allows you to build automation workflows (scenarios) between a wide range of third-party applications (2,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

Make offers a free plan which allows the creation of 2 scenarios with a limit of 1,000 operations per month, and paid plans start at $9/month for 10,000 operations.

Features

JobStaq provides support for:

• Triggers, which instantly starts a scenario when a record is created, updated, or deleted (configurable) in JobStaq
• Actions, which allow you to create, update and delete records in JobStaq from a scenario
• Searches, which allow you to locate records in JobStaq from a scenario
• API calls, which allow you to make arbitrary calls to the JobStaq API from a scenario, for advanced use cases where the built-in operations aren't flexible enough

At present, the integration supports the following record types:

• Customers
• Properties
• Jobs
• Employees
• Events
• Communications

Setup Process

1. Sign up for a Make account on Make's website, https://www.make.com/en/register.
2. Click here for the invite link to add the private JobStaq app to your Make account.
3. Generate an API key in the JobStaq web interface, by navigating to Company Settings > Developer > API Keys, or clicking here.
4. Create a new scenario for the first automation you wish to build with JobStaq. When adding the first JobStaq step to the scenario, you'll be prompted to connect an account. Enter the API key from the step above here, and click the continue button to authenticate Make 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.