Using ContactDrive with Zapier

Automatically import data from thousands of sources, and trigger workflows elsewhere when things happen in ContactDrive — without writing any code.

Setting it up

1. Add Zapier from the Apps marketplace.
2. Create an API key in Settings > API Keys. Name it "Zapier" so future-you knows what breaks if it's deleted.
3. In Zapier, add ContactDrive as an app and paste the key when asked to connect.

Choose the access level deliberately. If your Zaps only read from ContactDrive, a read-only key is all you need — and a read-only key that leaks is a much better problem than the alternative. If your Zaps create or update contacts, use custom scopes and grant exactly what they need.

What you can build

• Triggers — something happens in ContactDrive, and Zapier does something elsewhere. A new contact posts to Slack; a new donation adds a row to a spreadsheet.
• Actions — something happens elsewhere, and Zapier writes to ContactDrive. An Eventbrite registration becomes a contact; a Typeform submission logs an activity.

Zapier vs. webhooks

Zapier is the right choice when you want to connect to a service you don't want to write code for, and you're happy to have a third party in the middle.

Webhooks are the right choice when the service you're connecting already speaks webhooks — it's direct, immediate, and there's no Zapier task quota in the way. If both are options, prefer the webhook.