Zapier

Zapier connects Karani to apps Karani doesn’t integrate with directly — Google Sheets, Slack, Airtable, form builders, and several thousand others.

Getting your key

From Integrations, find the Zapier card and click Get Key.

The key is shown once

Copy it immediately and store it somewhere safe. If you lose it, use Refresh on the Zapier card to generate a new one — which invalidates the old one and breaks any Zaps using it.

What you can build

Zapier works with Karani’s webhooks and API.

Triggered by Karani — using webhooks:

• A new gift posts a message to a Slack channel
• A new contact is added to a Google Sheet
• An updated pledge notifies your team

Acting on Karani — using the API:

• A form submission creates a contact
• A calendar event creates a task
• A row added to a spreadsheet creates a gift

Webhook events

Karani fires webhooks on:

Event	When
contacts.create	A contact is created
contacts.update	A contact is updated
gifts.create	A gift is created
gifts.update	A gift is updated
pledges.create	A pledge is created
pledges.update	A pledge is updated
tasks.create	A task is created
tasks.update	A task is updated

Full detail in Webhooks.

Zapier vs. direct integration

If Karani has a direct integration for what you want — Mailchimp, QuickBooks, Stripe — use that. It’s purpose-built and handles the edge cases.

Zapier is for the things nobody built an integration for.

Start with a notification

A Zap that posts new gifts into a Slack channel takes ten minutes to build and is a surprisingly good morale feature for a team. It’s also an easy way to confirm your webhook plumbing works before you build something that matters.

Simpler alternatives

Before building a Zap, check whether Karani already does it:

• Getting data out regularly — exports
• Keeping a mailing list current — Mailchimp
• Collecting contacts from a web form — lead capture