Connect First AI Employee to Clientary.

CRM1 routeRoute facts checked August 28, 2026

This page shows every cataloged route for this app and marks the most capable working path. The recommended route is serving now after you authorize your own account.

You authorize and keep control of the provider account. No page view means an account is connected.

Recommended route

Dashboard-managed connection

Each completed call creates one uniquely event-numbered Clientary lead containing the caller identity and call summary, then reads the lead back before reporting delivery. This connection creates a lead only. It does not create a client, proposal, invoice, payment, project, task, or appointment.

Every available route

More than one route is shown when it adds a real capability or gives you a customer-owned alternative. Recommended means most capable today, not already connected.

Managed

Dashboard-managed connection

Serving now

Recommended route

What it does

Each completed call creates one uniquely event-numbered Clientary lead containing the caller identity and call summary, then reads the lead back before reporting delivery.

Before you start

Enter the Clientary account subdomain and API key for the workspace where inbound-call leads should land.

What it does not do

This connection creates a lead only. It does not create a client, proposal, invoice, payment, project, task, or appointment.

Set it up

Sign in to First AI Employee and open Integrations.
Enter the Clientary account subdomain and API key for the workspace where inbound-call leads should land.
Return to First AI Employee. The connected account is now used automatically for this integration.
Complete one non-production call and confirm the expected result appears exactly once in Clientary.

Set it up: Dashboard-managed connection

Enter the Clientary account subdomain and API key for the workspace where inbound-call leads should land.

Return to First AI Employee. The connected account is now used automatically for this integration.

Complete one non-production call and confirm the expected result appears exactly once in Clientary.

Verify the complete result

Complete one non-production call and confirm event-numbered lead creation and readback happened exactly once in Clientary.

Account ownership and data boundaries

The route sends only the event fields needed for the action you configure. Provider credentials stay in the approved connection or are sealed by First AI Employee where the guide explicitly says so.

Your provider and automation accounts remain yours.
A successful transport test is not the same as a verified provider write.
The pages never claim a native or two-way sync unless that exact capability exists.

Ready to connect it?

Use the dashboard to authorize your account. First AI Employee uses that account automatically, then you can test one complete downstream result.

Open Integrations in your dashboard Browse all app guides