← All integrationsVerified August 28, 2026
Seventeen vertical systems, without the logo wall.
This catalog separates working customer-owned Zapier recipes from vendor-gated paths. A read-only dashboard credential check is not automation. Where the dashboard card cannot perform the named write, the Zapier recipe is the recommended path and the credential preview is an alternative. Jobber, Workiz, Service Fusion, ISN, ServiceTrade, QuickBooks Online, HubSpot, Salesforce, Pipedrive, Clio, and shopVOX have useful customer-owned Zapier paths, subject to vendor permissions, required fields, and plan requirements. Canopy, EZLynx, ServiceWorks, Aesthetic Record, Spectora, and CampMinder still need additional fields, customer plan access, vendor approval, or work on our side.
Jobber
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: use a customer-owned Zap to create a Jobber client from a First AI Employee New Lead, then add a job or quote only when your intake supplies the fields you chose. The direct Jobber OAuth adapter is not open to customers today.
Jobber requires an active plan that includes its Zapier integration. Creating a client does not schedule work, and a job or quote needs customer-selected fields that are not present on every call.
How to enable it
- Install the private First AI Employee app in your Zapier account and connect your own Jobber account.
- Choose New Lead, then Jobber Create Client.
- Add a job or quote step only after mapping the required fields, then test one synthetic lead before activation.
Workiz
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: use a customer-owned Zap to map New Lead into Workiz Create Lead. Alternative: the dashboard can verify your API token and show a read-only credential preview, but that preview does not create leads, jobs, or bookings.
The Zapier route does not need Workiz's Developer API add-on. Create Job is only plausible after an added intake step supplies first name, address, city, postal code, start time, and a customer-selected job type. Normal call events should stay leads.
How to enable it
- Install the private First AI Employee app in Zapier.
- Choose New Lead, then Workiz Create Lead.
- Add Create Job only behind a filter for the required address, job type, and start time fields, then test the mapping.
Service Fusion
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: use a customer-owned Zap to map New Lead into Service Fusion Create Customer. Alternative: the dashboard can verify your client ID and secret and show a read-only credential preview, but that preview does not create customers, jobs, or estimates.
Job and calendar-task actions need additional account-specific fields and a tested multi-step Zap; normal call events should not be treated as scheduled jobs.
How to enable it
- Install the private First AI Employee app in Zapier.
- Choose New Lead, then Service Fusion Create Customer.
- Add Create Job or Create Calendar Task only after mapping the customer-selected fields and testing the Zap.
ISN
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: use a customer-owned Zap to find or create an ISN client from New Lead, with guarded order, calendar, or task steps when the required account fields are present. Alternative: the dashboard can verify your keys and show a read-only credential preview, but that preview does not create clients, orders, or appointments.
Inspection orders, calendar events, and tasks need account-specific inspector, user, time, and order fields that are not present in a normal call event.
How to enable it
- Connect ISN in your own Zapier account and install the private First AI Employee app.
- Use Find Client, then Create Client when no match exists.
- Add Create Order or Create Calendar Event only after choosing the account-specific inspector and time fields.
ServiceTrade
Recommended: useful automation through your Zapier accountWhat it can do: A First AI Employee New Lead trigger can find a contact by phone and create one when no match exists.
The Zap can continue only when the caller supplies a name and phone number. You choose the ServiceTrade contact type during setup. The workflow does not create a job, appointment, or invoice.
How to enable it
- Install First AI Employee in Zapier.
- Choose New Lead, then ServiceTrade Find Contact, and turn on Create ServiceTrade Contact if it does not exist.
- Choose your contact type, test the mapping, and turn on the Zap.
QuickBooks Online
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: after a caller becomes a real job, a customer-owned Zap can create the caller as a QuickBooks customer so a later estimate or invoice has the correct customer record.
QuickBooks Online is a premium Zapier app, so it needs a paid Zapier plan, a paid QuickBooks Online subscription, and QuickBooks admin permission. This recipe creates a customer only. It does not send an estimate, invoice, or charge.
How to enable it
- Connect your own QuickBooks Online account and install the private First AI Employee app in Zapier.
- Choose the qualified lead or booking trigger, then QuickBooks Online Create Customer.
- Map the caller identity, test with a synthetic customer, and confirm the record before activation.
HubSpot
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: a customer-owned Zap can find or create the caller as a HubSpot contact and attach the call summary without changing the contact's marketing subscription status.
HubSpot's free CRM can support this recipe, but the person who connects HubSpot to Zapier needs Super Admin permission. This workflow creates or updates a contact and call context, not a deal or marketing opt-in.
How to enable it
- Connect your own HubSpot account and install the private First AI Employee app in Zapier.
- Choose New Lead, find the contact by phone or email, and create the contact when no match exists.
- Attach the call summary, test the record, and leave marketing consent unchanged.
Salesforce
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: a customer-owned Zap can find or create a Salesforce lead or contact and carry the call summary into the record your team selected.
Salesforce is a premium Zapier app, so it needs a paid Zapier plan. The Salesforce edition, connected-app approval, and connecting user must also allow API access to the chosen objects and fields.
How to enable it
- Have a Salesforce administrator approve Zapier and confirm the connecting user can access the required object and fields.
- Install the private First AI Employee app, choose New Lead, and find or create the selected Salesforce record.
- Map the call summary, test one synthetic record, and confirm it appears once before activation.
Pipedrive
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: a customer-owned Zap can find or create the caller as a Pipedrive person, then create a lead and add the call summary as a note.
The customer must choose the pipeline, owner, and any account-specific fields during setup. This recipe does not mark a deal won, schedule an activity, or send a message.
How to enable it
- Connect your own Pipedrive account and install the private First AI Employee app in Zapier.
- Choose New Lead, find or create the person, then create a lead only when your team wants one.
- Add the call summary as a note, test the mapping, and activate the Zap.
Clio
Recommended: useful automation through your Zapier accountWhat it can do: Recommended: a law firm can use a customer-owned Zap to create a Clio Manage contact from a First AI Employee lead and keep the call summary with the intake record.
Clio Manage connects to Zapier; Clio Grow does not. Creating a matter needs additional firm-selected fields and a conflict-aware intake decision, so a normal call should create a contact first.
How to enable it
- Confirm the firm uses Clio Manage, then connect its own Clio and Zapier accounts.
- Install the private First AI Employee app, choose New Lead, and create the contact.
- Add a matter only behind the firm's reviewed intake process, then test with synthetic data before activation.
shopVOX
Needs fields or a required choiceWhat it can do: A customer-owned Zap can create a shopVOX sales lead with the caller and call summary.
The exact shopVOX pipeline name is required. Sign dimensions, materials, quantity, and deadline are not in the normal call event and need a separate intake step. This creates a sales lead, not an order or production job.
How to enable it
- Install the private First AI Employee app in Zapier.
- Choose New Lead, then shopVOX Create Sales Lead.
- Choose the exact pipeline and map caller and summary fields. Add sign specifications only after a separate intake step supplies them.
Canopy
Needs fields or a required choiceWhat it can do: A caller who supplies both first and last name can be found or created as an individual client.
With First AI Employee's current name-only mapping, the workflow cannot proceed without both name parts. That action has no phone field and does not add notes, tasks, appointments, billing, or files.
How to enable it
- Install First AI Employee in Zapier.
- Choose New Lead, then Canopy Find or Create Individual Client.
- Map Contact First Name and Contact Last Name. Leave leads without both names in First AI Employee.
EZLynx
Needs fields or a required choiceWhat it can do: Customers connect their own First AI Employee and EZLynx accounts inside Zapier, so they can build this recipe without giving EZLynx credentials to us. The Zap can find a personal applicant by cell phone and add the call summary after verifying the returned applicant.
The customer's EZLynx plan and user permission must allow Zapier. A shared household phone can match the wrong applicant, so stop on no match or ambiguity, verify the returned identity against the caller name when available, and pass a connected-account test before activation.
How to enable it
- Confirm that your EZLynx subscription and user permission include Zapier, then connect EZLynx in your own Zapier account. Do not send EZLynx credentials to First AI Employee.
- Install the private First AI Employee app, require a non-empty caller phone, search by cell phone, and require the returned identity to match the caller name when available.
- Map the verified Applicant ID, test and read back an approved non-production note, and only then activate the Zap.
ServiceWorks
Needs fields or a required choiceWhat it can do: Its Zapier app can create a customer when the workflow supplies first name, account number, phone, street, city, and state.
First AI Employee does not reliably have the account number and structured address on every call. Automatic writes stay off so we do not create partial customer records.
How to enable it
- Keep calls in the dashboard and verified report emails.
- Add a reviewed intake step that collects every required field.
- Only then map ServiceWorks Create Customer and test it.
Aesthetic Record
Vendor approval requiredWhat it can do: Its public Zapier app sends new-patient and new-invoice events out of Aesthetic Record. It has no action that accepts a First AI Employee lead.
Writing leads requires an Aesthetic Record Accelerator plan and partnership approval for its Leads Integration. Until both are in place, follow-up can use the practice booking URL.
How to enable it
- Confirm the practice has Aesthetic Record's Accelerator plan, then request approval from Aesthetic Record partnerships.
- Copy the practice booking URL until both requirements are met.
- Use that link for follow-up while call details stay in First AI Employee.
Spectora
Vendor access requiredWhat it can do: Spectora connects from your dashboard with a key you make yourself, read-only, and that is the route to use. Its Zapier and webhook lane is separate and is not live yet.
Spectora is generally available now, so nothing here waits on a vendor programme and you make your own key. What is still missing is the webhook lane: raw-body signature verification, durable dedupe, and tenant binding on our side, plus a signed webhook you create in your own Spectora developer account. Neither lane books inspections, and Spectora keeps inspections read-only in its own API.
How to enable it
- Make a key at developer.spectora.com and connect Spectora in your dashboard. The free tier allows 1,000 requests a month and is read-only.
- For the webhook lane, create the signed webhook in your own Spectora developer account.
- Wait for FAE to finish the signed route, tenant checks, dedupe, and record lookup before you rely on that lane.
CampMinder
Vendor access requiredWhat it can do: CampMinder offers a customer-gated API and private Zapier access, not a public app we can preconfigure for every customer.
A CampMinder administrator must generate API and subscription keys and obtain written vendor permission before those credentials can be used. The safe fallback is the camp application or inquiry link.
How to enable it
- Ask the CampMinder administrator to confirm API or private Zapier access and generate the required API and subscription keys.
- Do not share or store either key until the vendor approves the use.
- Use the camp application or inquiry link while approval is pending.
Already a customer?
The Integrations page in your dashboard shows the same requirements, your current First AI Employee Zap status, and the exact setup steps.