Skip to main content
Find it in Darwin Settings → API → API keys Open API settings ↗
Darwin’s Zapier app starts a Zap the moment something happens in your website chat: a visitor leaves their name and email, books a meeting, or asks for a person. Zapier then does the rest in the tools you already use, such as creating the contact in your CRM or posting to your team’s channel.
Darwin is in private beta on Zapier. Use the link in step 1 to add it to your Zapier account. It then appears in the Zap editor like any other app.
1

Add Darwin to your Zapier account

Sign in to Zapier, then open the Darwin invite link and accept the invite.
2

Create a key for Zapier in Darwin

In Darwin, open Settings → API and select Create key. Name it Zapier. Under Access, select Choose and tick:
  • webhooks:write so Zapier can start your Zaps the moment an event happens
  • events:read so Zapier can confirm each event with Darwin
  • contacts:read so names and emails reach the Zap
  • conversations:read and meetings:read for conversation and meeting details
Add contacts:write if a Zap should create or update contacts in Darwin, and knowledge:write if it should add knowledge. Select Create key and copy it. Darwin shows the key once.
3

Connect Darwin in a Zap

In Zapier, create a Zap and search for Darwin as the trigger app. Choose an event, connect a new Darwin account, and paste the key. The connection is named after your workspace.
4

Test and publish

Select Test trigger. Zapier shows your three most recent matching events, or a sample if the workspace has none yet. Add your action, test it, and publish the Zap.Darwin now lists the Zap’s subscription under Settings → API → Webhooks, named Zapier: followed by the trigger.

​
Triggers

Each trigger is instant: Darwin sends the event to Zapier as it happens. Lead, person-request and conversation triggers include the visitor’s name, email, company and phone when given, the page they chatted on, their traffic source and UTM values, Darwin’s grade (intent, buying stage, qualification score), the reason they asked for a person, and a Darwin url that opens the conversation in Darwin.

​
Actions and searches

HubSpot

New leads become HubSpot contacts with the conversation attached.

Salesforce

New leads become Salesforce leads, owned by the right rep.

Pipedrive

New leads become a person and a deal in your pipeline.

Slack

Post to a channel when a lead arrives or a visitor asks for a person.

Microsoft Teams

The same alerts, in a Teams channel.

Mailchimp

Add new leads to an audience with a tag.

ActiveCampaign

Add new leads to a list or an automation.

Klaviyo

Add new leads to a list as profiles.

​
Test safely

Conversations you have in the Agent Studio preview never start a Zap, so testing your agent won’t fill your CRM. To check a Zap end to end, chat on your live website and give a real name and an email address you own, or use the samples from Test trigger while you build.
Open the invite link in step 1 while signed in to the Zapier account you build Zaps in, and accept the invite. Then search for Darwin again.
Darwin names the missing scope, for example webhooks:write. Create a new key with that scope ticked, then reconnect Darwin in Zapier under Apps → Darwin.
Check Settings → API → Webhooks in Darwin. The Zap’s subscription should be listed and on. Deliveries shows each event Darwin sent and Zapier’s response. If the subscription is missing, turn the Zap off and on again.
Every Zap using it stops, and Zapier asks you to reconnect. Create a new key and update the connection under Apps → Darwin in Zapier.
Webhooks and the API → · Send handoffs to Slack with code →