Connect First AI Employee to HubSpot.

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 works through automation you configure and own.

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

Recommended route

Customer-owned Zapier workflow

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.

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.

Zapier

Customer-owned Zapier workflow

Customer setup required

Recommended route

What it does

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.

Before you start

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.

What it does not do

Set it up

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.

Provider documentation

Set it up: Customer-owned Zapier workflow

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.

Verify the complete result

Use synthetic data, confirm the downstream record once, and only then activate the workflow.

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, select the customer-owned destination, and test the complete downstream result.

Open Integrations in your dashboard Browse all app guides