What it connects to.

This is the preferred connection for Cloudbeds, and it needs no Zapier account. Paste a Cloudbeds property API key, choose the verified property, then choose the room type and reservation defaults your receptionist may use. The connected lane looks up reservations and guests by ID and creates one-room reservations after it collects the required guest and stay details.

Worth knowing: Cloudbeds must issue a key with guest and reservation read access plus permission to create reservations. The key is stored sealed after you choose the property it serves. This lane cannot collect card details, charge payments, or modify existing reservations.

Add a report recipient under Channels. Your signup address starts with one click; any other address must verify its confirmation link before call reports and transcripts are sent there.

Every call, transcript, recording and booking lands in your dashboard as it happens. It is the one place that always has the whole record.

Your dashboard generates the account-bound script and gives exact placement steps for WordPress, Squarespace, Wix, Shopify, Webflow and other sites. Paste it, publish, then send a real message to prove it is live.

Worth knowing: Requires an active AI Chat & Replies plan. The widget is our own secure embed, not a third-party chat account.

The connection flow stays unavailable until the Meta app credentials are configured and the dashboard can prove the Page connection is ready. No dead Connect button is offered in the meantime.

Connect it once from your dashboard. Your AI reads your free and busy times during the call, then writes the appointment to the calendar you picked. If the calendar is ever unreachable, it takes the request and tells the caller it is recorded, never that it is booked.

Connect it once from your dashboard and your AI writes appointments straight onto your Outlook calendar. Live availability checking is newer here than on Google: where it cannot read your calendar it takes the appointment and says so, instead of guessing a time that might already be taken.

Worth knowing: Needs a Microsoft 365 business account. Personal Outlook.com and Hotmail addresses cannot connect.

Connect it once, then choose the active event type your AI should book. During the call it reads Calendly availability, asks for the caller’s email, and confirms only after Calendly returns the scheduled event.

Connect it once, then choose the event type your AI should book. It reads availability for that event type during the call and confirms only after Cal.com creates the booking and hands it back.

Connect it once, then choose the booking calendar your AI should use. It reads the open times on that calendar and confirms only after OnceHub creates the booking and hands it back.

For resource bookings. Connect it, then enter the site, the resource and the quantity your AI should reserve. It checks that resource and creates the reservation with force-booking off, so a full resource stays full.

Worth knowing: Planyo returns a reservation number but gives this connection no way to read the reservation back, so your AI reports the number and nothing more.

Connect it with your API key, then choose the meeting type. Your AI submits a meeting request and says the request was received. It never tells a caller the meeting is confirmed, because CalendarHero confirms it later.

Your AI cannot read Acuity for live availability, so it will not quote a time from it. What it does instead: text the caller your booking link, and drop the lead into Acuity the moment the call ends. Acuity takes the person but not the appointment, so somebody still books that one.

Under Channels, authorize Slack and choose the channel on Slack’s own screen.

Under Channels, make a Teams Workflow and paste the webhook it gives you.

Under Channels, authorize private report DMs or paste a webhook for a shared channel.

Under Channels, open the link and press Start on the bot. Nothing is pasted into the dashboard.

The linking code and Signal number appear only on a deployment with the Signal service configured. That service is not configured today, so Signal is not offered as a live channel.

Under Channels, link the Chat app with its one-time code or paste a webhook for a shared space.

Call recaps on WhatsApp are coming soon. The available channels above can be connected today; Signal remains unavailable until its service is configured.

Recommended today: install the private First AI Employee app in your own Zapier account, choose New Lead, and use Jobber Create Client. This creates a client only. Requests, jobs, visits, quotes and invoices need separately reviewed fields and actions. The direct OAuth card remains closed.

Worth knowing: Your Jobber plan and user must permit Zapier and client creation. Send a synthetic lead and confirm the client in Jobber before turning the Zap on.

For pest and other home-service teams. Install the private First AI Employee app in your own Zapier account, choose New Lead, and use FieldPulse Create Lead. A separate reviewed recipe can find or create the customer and create a job when the intake has Customer Id, Job Title, Start time and End time.

Worth knowing: This is customer-owned Zapier automation, not a native or two-way sync. FieldPulse Create Lead requires First_name; Create Job requires Customer Id, Job Title, Start time and End time.

For pest and other recurring home-service teams. Install the private First AI Employee app in your own Zapier account, choose New Lead, and use GorillaDesk Add Customer. Add Booking is a separate reviewed step after the intake has the required schedule and service-location fields.

Worth knowing: This is customer-owned Zapier automation, not a native or two-way sync. Add Booking requires Start DateTime, Email, Mobile Phone and Address, so the compact lead handoff does not book by itself.

The dashboard can verify a JobNimbus API key and the company it reaches, but this does not sync calls or create CRM records. No customer-ready JobNimbus write route is enabled today.

Worth knowing: JobNimbus must issue an API key that can read your company. Where one key sees more than one company you have to choose, so a shared admin key cannot attach itself to the wrong business.

This is the preferred connection for Workiz, and it needs no Zapier account. Paste the token and secret once. Each completed call with the required caller identity creates one Workiz lead with the caller details, call summary, and a stable event marker.

Worth knowing: The Workiz API needs the Ultimate plan with the Developer API add-on. This lane creates a lead only, not a customer, job, appointment, quote, invoice, or payment. Workiz publishes no read that accepts the secret, so we store it sealed without claiming that the secret itself was proven.

This is the preferred connection for Service Fusion, and it needs no Zapier account. Each completed call matches a customer by exact phone or creates one, then creates one marker-backed Job with the call details.

Worth knowing: The Service Fusion API needs the PRO plan. The result is a captured Job, not a scheduled Visit or confirmed calendar booking. Accounts that require additional job defaults may reject the minimal Job until those account rules are configured.

This is the preferred connection for ISN, and it needs no Zapier account. Each completed call with a name and phone matches a client by exact phone or creates one client with the caller details.

Worth knowing: This lane does not create an order, inspection, or appointment. An ISN access key never expires and carries the full rights of the user who made it, so use the least privileged account that can read and create clients. When you disconnect, delete the key in ISN as well.

The dashboard can verify a Spectora API key, but this does not create clients or inspections. No customer-ready Spectora write route is enabled today.

Worth knowing: Self-serve Spectora keys are read-only. Spectora offers contact writes only on its separate Standard API plan, and its public API does not publish inspection creation. This connection remains a credential preview.

One approval screen from your dashboard, on your own Follow Up Boss account. Each completed call files an Incoming Call lead event carrying the caller name, phone number and the summary. Appointments and deals are left alone on purpose: those are decisions, and a decision belongs to a human.

One approval screen from your dashboard, on your own RepairShopr account. Each completed call creates an unconverted lead with the caller first name, last name and phone number. It does not open a ticket, create a customer or put anything on your schedule.

One approval screen from your dashboard, on your own CompanyCam account. Each completed call creates a customer record with the caller name, phone number and the call summary. It does not create projects or tasks, because those need an address and a decision we do not have.

One approval screen from your dashboard, on your own Táve account. Each completed call creates a lead-stage job carrying the caller identity and the call summary. Events and bookings stay yours to create.

Connect your own HighLevel sub-account in one approval screen from your dashboard. After that, every completed call creates or updates the caller as a contact and adds the call summary as a note. It does not create opportunities, tasks or appointments, and it never sends an outbound message.

Worth knowing: You need admin access to the HighLevel sub-account where completed calls should land. Composio, our integration partner, holds the approved connection for us.

Paste a Housecall Pro MAX-plan Admin API key in the dashboard. Your receptionist reads existing jobs as busy time, matches or creates the caller as a customer, and writes either a scheduled job or a lead according to the mode you choose.

Worth knowing: Lead mode captures the caller but does not reserve time. Scheduled job mode needs a service address and business time zone, and counts as booked only when Housecall Pro returns a job ID. If the job write cannot be supported, the adapter falls back to a lead.

Your ServiceTitan admin completes ServiceTitan’s Zapier registration, builds the downstream action in your own Zapier account, and pastes that Zap’s Catch Hook into the dashboard. We deliver completed-call data to the hook in one direction. What Zapier writes into ServiceTitan is the workflow you configure, not a native or two-way First AI Employee sync.

Worth knowing: Needs the Works or Legacy package, plus a form ServiceTitan reviews before they issue credentials. Their Zapier app is in open beta and ServiceTitan does not formally support it.

Onfleet is available through your own Zapier account and the Catch Hook fallback in your dashboard. There is no direct managed Onfleet connection yet.

Authorize the correct QuickBooks company once. Each completed call with a valid phone number is matched or created as a customer record. The connection cannot create invoices, estimates, payments, refunds, charges or any other money record.

Worth knowing: The managed connection must be enabled in your dashboard. Complete one non-production call and confirm that exactly one customer appears before relying on it.

Authorize HubSpot once. Each completed call checks the exact phone number and creates the contact only when it is absent. Existing contacts, deals, meetings, campaigns and outbound messages are left alone.

Paste your Nutshell account email and API key once. Each completed call finds the caller by exact phone, creates one contact when none exists, and attaches one completed-call note. It never enrolls contacts in marketing, sends messages, or deletes records.

Worth knowing: Create the key in ordinary Nutshell Settings under Connections, API keys. No developer account, OAuth app, or vendor review is required.

Paste your folk API key once. Each completed call finds the caller by exact phone, creates one person when none exists, and attaches one completed-call note. It never enrolls people in marketing, sends messages, or deletes records.

Worth knowing: Create the key in your folk workspace under Settings, API. No developer account, OAuth app, or vendor review is required. folk API access requires its Premium plan.

Authorize Capsule once. Each completed call finds the caller by exact phone, creates one person when absent, and attaches one private call note with a stable event marker.

Worth knowing: The connection cannot send messages, delete records, or change pipelines and opportunities.

Authorize Intercom once. Each completed call finds the caller by exact phone, creates one lead when absent, and attaches one private call note with a stable event marker.

Worth knowing: A phone call is not marketing consent. This connection cannot start conversations, send messages, change subscriptions, or create campaigns.

Authorize the Attio workspace once. Each completed call finds or creates the person by exact phone and adds one call note, which is read back before the delivery counts as done.

Authorize the Dynamics organization once. Each completed call creates one lead carrying a stable marker and reads it back. Appointments and opportunities stay with your people.

Paste your Ascora API key once. Each completed call makes sure the caller exists as a customer with their phone number, then attaches the call note. Jobs and appointments stay with your people.

Worth knowing: The connection screen verifies the key before any completed call is delivered.

Paste your Clientary subdomain and API key once. Each completed call creates one lead with its own number and reads that lead back before the delivery counts as done.

Paste your account URL and API key once. When the caller already exists as a contact matched by phone, each completed call adds one marked note and reads it back. A caller who is not in ActiveCampaign is left for your follow-up, because this connection will not invent an email address to create one.

Worth knowing: A phone call is not marketing consent. The connection cannot add anyone to a list, an automation or a campaign.

Authorize the Salesforce organization once. Each completed call checks the exact phone number and creates a lead only when it is absent. Opportunities, tasks, events and messages remain human-controlled.

Worth knowing: Your Salesforce edition and user must allow API access. Salesforce requires a Company value, so consumer callers are explicitly labelled as individual callers instead of being assigned a guessed employer.

Authorize the Zoho CRM organization once. Each completed call checks the exact phone number and creates a lead only when it is absent. Deals, tasks, events, campaigns and outbound messages remain human-controlled.

Worth knowing: Automations already configured in your Zoho account may react to a newly created lead. Test once in the intended organization before relying on it.

Authorize the Square account once. Each completed call with a valid phone number is matched or created as a customer record. The connection cannot create appointments, orders, invoices, cards, charges, refunds or payments.

Authorize Pipedrive from the dashboard. Each completed call with a valid phone number finds or creates a phone-backed person. Leads, deals, activities and outbound messages remain human-controlled; a customer-owned Zapier recipe is available when you want those extra steps.

For law firms. New callers land as a contact or a matter.

Worth knowing: Clio Manage connects to Zapier. Clio Grow does not, which is worth knowing before you plan your intake around it.

Connect your Google account, choose a spreadsheet and sheet, and every completed call becomes one row with the caller details and summary. No n8n account, import or webhook is needed.

Worth knowing: The card becomes Ready only after the provider approval and destination check both succeed. If the card is not offered in your dashboard, the managed connection is not enabled for your account yet.

Authorize Airtable, choose a base and table, and map an Event ID text field plus a long-text details field. Every completed call creates one marker-backed record.

Worth knowing: The connection cannot delete records, alter a base schema, send messages, or change Airtable automations.

Authorize Google Drive once. First AI Employee automatically finds or creates a private First AI Employee Call Notes folder and writes one text note for each completed call.

Worth knowing: The connection cannot delete, share, publish, move or update Drive files. Complete one non-production call and confirm that exactly one private note appears.

Approve your Notion account and choose a database. Every completed call creates one page containing the caller details and call summary.

Worth knowing: The card becomes Ready only after the selected database is verified with your approved account.

Approve your Asana account and choose a project. A completed call creates one task only when follow-up is needed.

Worth knowing: The card becomes Ready only after the selected project is verified with your approved account.

Authorize Todoist once. First AI Employee automatically finds or creates a First AI Employee Follow-ups project and creates one task only for calls explicitly marked as needing follow-up.

Worth knowing: The connection cannot delete or complete tasks. Complete one non-production follow-up call and confirm that exactly one task appears.

Authorize Google Tasks once. First AI Employee finds or creates a dedicated First AI Employee task list and creates one task only for calls explicitly marked for follow-up.

Worth knowing: The connection cannot delete or complete tasks. A stable event marker prevents retry duplicates.

Approve your ClickUp account and choose a list. A completed call creates one task only when follow-up is needed.

Worth knowing: The card becomes Ready only after the selected list is verified with your approved account.

Approve your Trello account, then choose a board and list. A completed call creates one card only when follow-up is needed.

Worth knowing: The card becomes Ready only after the selected board and list are verified with your approved account.

Anything with a Zapier app is reachable the same way. If you already run it, we will look at it with you during onboarding.

Mindbody, Vagaro, Booksy, Fresha and GlossGenius publish no Zapier app, so nobody can connect them this way, us included. That is their decision, not a gap on our side, and no amount of building here changes it. What works today: your AI answers, takes the booking details, and sends them to you by email, chat and dashboard. Square is the exception worth knowing about. It connects on a free account and it can create the appointment, not just the client.

ServiceM8 and AccuLynx still need account-specific fields before we can offer a managed native connection. ServiceM8 will not create a job without a street address. AccuLynx will not create a contact without a contact type that only exists inside your own account. GorillaDesk now has a customer-owned Zapier Add Customer path in the vertical-software dashboard and marketing page; its native/managed connection still waits because booking needs a complete service address, a phone type from the account, and duplicate-safe handling.

These are real pest-management systems with documented or vendor-backed API paths, but each requires tenant credentials, account-specific scheduling defaults, and provider approval or a test tenant before we can offer a managed appointment write. They are listed with their exact requirements on the vertical-software page.

During managed setup, we read destination names and IDs so you can choose the right spreadsheet, database, project, list or board. Before each managed write, we check only for our event marker in the selected sheet, a matching Notion page title and marker block, or task and card names so a retry does not create a duplicate. We do not import or synchronize the rest of your account. Google Calendar, Outlook and Calendly also read availability because booking a real time depends on it.

Tell us what you run during the consultation. If it has a safe managed connection or Zapier reaches it, we will tell you the shortest supported route. If neither does, we will say so before you pay.