CRM integration.
Two CRMs supported: HubSpot and Pipedrive. Connecting one (or both) lets every captured lead flow automatically into your existing pipeline.
What syncs to your CRM
| Trigger | HubSpot action | Pipedrive action |
|---|---|---|
| Lead captured | Upsert Contact; create Deal “Tenlo Lead — [name]“ | Upsert Person; create Deal “Tenlo Lead — [name]“ |
| Lead scored 60 or higher | Move Deal forward to Qualified to buy | Move Deal forward to your Qualified stage |
| Meeting booked | Move Deal forward to Presentation scheduled | Move Deal forward to your demo / meeting stage |
| Booking cancelled | No automatic action — manual follow-up | No automatic action |
Two rules apply to both CRMs:
- Tenlo never closes a deal. A good score or a booked meeting isn’t a sale, so Tenlo never marks a deal won or lost. That stays your call.
- Deals only move forward. If a deal is already further along, including anything you moved by hand, Tenlo leaves it where it is. A late score never pulls a booked deal back.
HubSpot deal stages
New deals start at Appointment scheduled, the first stage of HubSpot’s default pipeline.
| Event | HubSpot stage |
|---|---|
Score 60 or higher (good_fit or hot) | qualifiedtobuy |
Score under 60 (low_fit) | no change |
| Meeting booked | presentationscheduled |
These are HubSpot’s default deal pipeline stages. On a custom pipeline the deal is still created and kept up to date with the contact, but Tenlo doesn’t move it between stages. Contact support if you’d like it aligned.
Pipedrive deal stages
Pipedrive stage names are yours, so Tenlo matches on the name, in the deal’s own pipeline:
- Score 60 or higher → the first stage with qualif in its name (e.g. “Qualified”).
- Meeting booked → the first stage with demo, meeting, appointment, scheduled or booked in its name (e.g. “Demo Scheduled”).
If no stage name matches, the deal stays where it is. Won and lost deals are never touched.
Pipedrive deals are linked to the Person only — no Organisation is created for P05 leads, because the chat doesn’t reliably capture company info. If you need Org-level pipeline tracking, create and link the Organisation manually. On the roadmap once company info is reliably available from the conversation.
Connecting HubSpot
Top nav → Settings → Integrations → HubSpot → Connect HubSpot → OAuth flow → Approve permissions. Leads start syncing immediately.
Connecting Pipedrive
- Get a personal API token from Pipedrive (Personal preferences → API).
- Paste it into Settings → Integrations → Pipedrive.
- (Optional) Add company domain (e.g.
acmecorpforacmecorp.pipedrive.com).
Pipedrive uses personal API tokens, not OAuth. If the user who created the token leaves the company, generate a new token from someone with permanent access.
What happens if both are connected
Both fire on every event. You get duplicate records — one in HubSpot, one in Pipedrive. Pick one, not both, unless you have a clear migration reason.
Disconnecting
Settings → Integrations → Disconnect. Tokens are wiped. Existing CRM records aren’t touched — only future syncs stop.
What doesn’t sync
- The conversation transcript (lead reasoning is synced as a property on the Contact, but the full chat is not)
- Custom fields beyond name/email/phone/score
- Marketing campaign attribution
These are roadmap items.