Twenty-one vertical systems, without the logo wall.

Jobber

What 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

1. Install the private First AI Employee app in your Zapier account and connect your own Jobber account.
2. Choose New Lead, then Jobber Create Client.
3. Add a job or quote step only after mapping the required fields, then test one synthetic lead before activation.

FieldPulse

What it can do: Recommended: a customer-owned Zap can create a FieldPulse lead from a First AI Employee New Lead, then a separate reviewed recipe can find or create the customer and create a job when the intake has complete schedule fields.

FieldPulse Create Lead requires First_name. Create Job requires Customer Id, Job Title, Start time, and End time, so the compact lead path does not schedule work by itself. This is customer-owned Zapier automation, not a native or two-way sync.

How to enable it

1. Install the private First AI Employee app in your Zapier account and connect your own FieldPulse account.
2. Choose New Lead, then FieldPulse Create Lead, and map the caller and summary fields.
3. For scheduled work, add Find or Create Customer and Create Job only after the intake supplies Customer Id, Job Title, Start time, and End time. Test one synthetic booking before activation.

GorillaDesk

What it can do: Recommended: a customer-owned Zap can add a GorillaDesk customer from a First AI Employee New Lead and preserve the call summary.

The compact lead path uses Add Customer, which requires First Name. GorillaDesk Add Booking also requires Start DateTime, Email, Mobile Phone, and Address, so scheduling needs a richer reviewed intake and a separate customer-owned Zapier step. This is not a native or two-way sync.

How to enable it

1. Install the private First AI Employee app in your Zapier account and connect your own GorillaDesk account.
2. Choose New Lead, then GorillaDesk Add Customer, and map the caller, phone, email, company, and summary fields.
3. Add Add Booking only after a richer intake supplies Start DateTime, Email, Mobile Phone, and Address. Test the downstream record before activation.

Workiz

What it can do: Preferred when direct delivery is available: connect Workiz in the dashboard. First AI Employee verifies the account, reads bounded lead history to reconcile repeats, and writes one marker-backed Workiz lead for each eligible completed call. Alternative: a customer-owned Zap can map New Lead into Workiz Create Lead.

The direct route needs Workiz's Ultimate plan with the Developer API add-on and creates leads only, not jobs or appointments. Workiz publishes no read that accepts the secret, so the dashboard check proves the token and the first successful lead write proves the secret. The Zapier alternative does not need that add-on. Use Zapier Create Job only after intake supplies first name, address, city, postal code, start time, and a customer-selected job type.

How to enable it

1. When direct delivery is available, paste your Workiz API token and secret in the dashboard.
2. Confirm the token check, then let eligible completed calls create marker-backed Workiz leads automatically.
3. Use the customer-owned Zapier alternative when direct API access is unavailable or when a guarded Create Job step has every required scheduling field.

Service Fusion

What it can do: Preferred when direct delivery is available: connect Service Fusion in the dashboard. First AI Employee verifies the account, matches a customer by exact phone or creates one, and writes one marker-backed Job with the completed-call details. Alternative: a customer-owned Zap can create the customer and add guarded follow-up actions.

The direct route needs Service Fusion's PRO plan. It records an unscheduled Job, not a scheduled Visit or confirmed booking, and an account with extra required job defaults may reject the minimal Job. Use the Zapier alternative for account-specific Create Calendar Task steps.

How to enable it

1. When direct delivery is available, paste your Service Fusion client ID and secret in the dashboard.
2. Confirm the connection, then let eligible completed calls match or create the customer and write one marker-backed Job.
3. Use the customer-owned Zapier alternative when direct API access is unavailable or when you need a tested calendar-task flow with account-specific fields.

ISN

What it can do: Preferred when direct delivery is available: connect ISN in the dashboard. First AI Employee verifies the account and company key, finds clients by exact phone, and creates one client for an eligible completed call when no match exists. Alternative: a customer-owned Zap can add guarded order, calendar, or task steps.

The direct route creates clients only, not inspection orders or appointments. ISN keys do not expire and carry the full permissions of the user who created them, so use the least-privileged suitable account. Orders, calendar events, and tasks remain Zapier alternatives because they need account-specific inspector, user, time, and order fields.

How to enable it

1. When direct delivery is available, paste your ISN access key, secret, company key, and account host in the dashboard.
2. Confirm the identity and company-key checks, then let eligible completed calls match or create ISN clients by exact phone.
3. Use the customer-owned Zapier alternative only for guarded Create Order, Create Calendar Event, or Create Task steps with every required account choice.

QuickBooks Online

What 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

1. Connect your own QuickBooks Online account and install the private First AI Employee app in Zapier.
2. Choose the qualified lead or booking trigger, then QuickBooks Online Create Customer.
3. Map the caller identity, test with a synthetic customer, and confirm the record before activation.

HubSpot

What 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

1. Connect your own HubSpot account and install the private First AI Employee app in Zapier.
2. Choose New Lead, find the contact by phone or email, and create the contact when no match exists.
3. Attach the call summary, test the record, and leave marketing consent unchanged.

Salesforce

What 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

1. Have a Salesforce administrator approve Zapier and confirm the connecting user can access the required object and fields.
2. Install the private First AI Employee app, choose New Lead, and find or create the selected Salesforce record.
3. Map the call summary, test one synthetic record, and confirm it appears once before activation.

Pipedrive

What 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

1. Connect your own Pipedrive account and install the private First AI Employee app in Zapier.
2. Choose New Lead, find or create the person, then create a lead only when your team wants one.
3. Add the call summary as a note, test the mapping, and activate the Zap.

Clio

What 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

1. Confirm the firm uses Clio Manage, then connect its own Clio and Zapier accounts.
2. Install the private First AI Employee app, choose New Lead, and create the contact.
3. Add a matter only behind the firm's reviewed intake process, then test with synthetic data before activation.

shopVOX

What 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

1. Install the private First AI Employee app in Zapier.
2. Choose New Lead, then shopVOX Create Sales Lead.
3. Choose the exact pipeline and map caller and summary fields. Add sign specifications only after a separate intake step supplies them.

Canopy

What 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

1. Install First AI Employee in Zapier.
2. Choose New Lead, then Canopy Find or Create Individual Client.
3. Map Contact First Name and Contact Last Name. Leave leads without both names in First AI Employee.

EZLynx

What 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

1. 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.
2. 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.
3. Map the verified Applicant ID, test and read back an approved non-production note, and only then activate the Zap.

ServiceWorks

What 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

1. Keep calls in the dashboard and verified report emails.
2. Add a reviewed intake step that collects every required field.
3. Only then map ServiceWorks Create Customer and test it.

Aesthetic Record

What 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

1. Confirm the practice has Aesthetic Record's Accelerator plan, then request approval from Aesthetic Record partnerships.
2. Copy the practice booking URL until both requirements are met.
3. Use that link for follow-up while call details stay in First AI Employee.

Spectora

What 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

1. 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.
2. For the webhook lane, create the signed webhook in your own Spectora developer account.
3. Wait for FAE to finish the signed route, tenant checks, dedupe, and record lookup before you rely on that lane.

CampMinder

What 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

1. Ask the CampMinder administrator to confirm API or private Zapier access and generate the required API and subscription keys.
2. Do not share or store either key until the vendor approves the use.
3. Use the camp application or inquiry link while approval is pending.

FieldRoutes / PestRoutes

What it can do: FieldRoutes has tenant-specific customer, subscription, service-type, availability, appointment, and note operations, but First AI Employee does not enable a customer connection until the vendor contract and tenant setup are complete.

The API needs an authentication key and token plus account-specific service type, office, route, employee, note type, and timezone values. Public documentation is not a self-serve customer connection, so no automatic pest appointment write is promised here.

How to enable it

1. Ask FieldRoutes for tenant credentials and confirmation that external appointment creation is enabled.
2. Provide the service type, office, route, employee, note type, and timezone values the receptionist should use.
3. Supply a non-production tenant so customer lookup, availability, appointment write, and readback can be implemented and verified.

PestPac

What it can do: PestPac is a common pest-management system with a WorkWave integration path, but the customer-facing API contract and write permissions must be issued for the account before First AI Employee can build a safe adapter.

The public integration material does not provide a self-serve connector with the production authentication, appointment schema, and tenant permissions needed for an automatic booking write. Vendor approval, customer credentials, and a test tenant remain required.

How to enable it

1. Ask PestPac or WorkWave to approve the integration and issue the current API or partner-access documentation for the customer tenant.
2. Provide tenant credentials, service and route defaults, and the exact customer and appointment fields the receptionist should write.
3. Run a non-production customer and appointment readback before any live pest calls use the adapter.

Briostack

What it can do: Briostack documents a REST API and sandbox. Every request uses the subscriber's unique instance subdomain and an x-api-key header, with either an Integration Partner API Key or a subscriber-specific User API Key.

API access is tied to a Briostack subscription. A subscriber can enable a registered Integration Partner application, or an authorized user can create a User API Key in My Account. First AI Employee still needs an adapter, account-specific scheduling defaults, and a non-production write and readback test before enabling live calls.

How to enable it

1. Choose the Briostack access path: an Integration Partner API Key for a registered application or a User API Key created by an authorized user in the subscriber instance.
2. Complete secure setup with the subscriber's unique instance name, branch, service, and scheduling defaults, and the key used as the x-api-key header.
3. Use a non-production Briostack instance to prove customer creation, appointment writes, and readback before enabling live calls.