Zapier integration

Connect Zapier today through its web request step. Kirora’s own Zapier app is built and will be submitted for listing in Zapier’s directory; until then, use a Kirora API key: Integrations › Zapier in Kirora lists the steps to send contacts and events. To start a Zap from Kirora events, add the webhook URL Zapier gives you on Kirora’s Webhooks page. Zapier’s own webhook step can’t check Kirora’s signature, so treat that URL as a secret.

Connect Zapier to Kirora to move contacts, events and messages between Kirora and the apps you already use, without writing code. Kirora’s events can start your Zaps, and your Zaps can add contacts, record events and send email in Kirora.

Before you start

Maintained by: Kirora, for the Zapier app; Zapier, for its own web request and webhook steps.
Direction: both ways, from Kirora’s events into Zapier and from your Zaps into Kirora.
You need: a Zapier account and a Kirora API key, which an admin or the owner creates under Integrations › Zapier. See which plans include it.

What it does

Triggers. Kirora sends each event to Zapier through a webhook subscription, so Zapier doesn’t need to poll.

New contact: a contact is created.
Contact unsubscribed: someone opts out through an email’s unsubscribe link.
Form submitted: someone submits one of your Kirora forms.
Message sent, opened or clicked: an email or push moves through delivery. Opens and clicks fire on the first one, and an open can come from a mail app’s privacy feature rather than the person.
Message delivered or bounced: the recipient’s mail server accepts or rejects an email. Delivered doesn’t say whether it reached the inbox or spam.

Actions. Zapier can do this in Kirora:

Create or update contact, by email or your own external ID.
Track event on a contact, found by email, external ID or Kirora ID. Events start journeys and fill segments.
Add contact to list.
Send transactional message: one email, from a stored template or written in the step.
Find contact by email.

In Zapier, Find contact pairs with create as Find or create contact.

Connect the native Zapier app when listed

These steps apply once Kirora’s app is listed in Zapier’s directory. Until then, use the web request route above.

In Kirora, go to Integrations › Zapier and choose New key. Admins, developers and the owner can create keys, and the key is shown once. The scopes Zapier needs are already ticked, except that a developer’s key leaves out managing list members and sending transactional email. For those steps, ask an admin or the owner for the key.
In Zapier, add a Kirora connection and paste the key, which starts with kirora_, into API key. Kirora checks it straight away and names the connection after your workspace.
Turn on a Zap that starts from a Kirora trigger. It subscribes itself to that event, and unsubscribes when you turn it off. The Webhooks page in Kirora lists the subscriptions Zapier created.

Matching: Kirora’s identify call (POST /v1/contacts/identify) finds the contact by your external ID, then email, then phone, and creates it if none matches. Tracking an event on a contact that doesn’t exist yet fails, so create or update the contact first.
Consent: a contact your Zaps create has no marketing consent unless the step grants it, and granting it needs a statement of how the person agreed. Withdrawing consent needs none.

Test it

Run a Zap that creates or updates a contact with your own email address. The contact appears in Contacts in Kirora, and the call shows under Recent calls on Integrations › Zapier.
To test a trigger, add the webhook URL Zapier gives you on Developer › Webhooks and choose Send test event. Zapier receives a webhook.test delivery, and Recent deliveries shows Zapier’s response.

Use it for

New sign-ups from your other tools: create or update a Kirora contact when someone signs up in an app that has no direct connection, and track the event so a welcome journey starts.
Leads to your sales tools: when someone submits a Kirora form, send their details to your CRM or a spreadsheet.
A team alert for bounces: post a message to your team’s chat when an important email bounces.

Limitations

Triggers send each event at least once, and not always in order.
A paused webhook, or one Kirora turned off after repeated failures, receives no new events, and events that happen meanwhile aren’t kept for it.
Kirora records a tracked event once for each Idempotency-Key, within your plan’s event history. Use something that identifies the action, such as an order ID, so a Zap that runs again doesn’t record it twice.

Get help

Integrations › Zapier shows each call your Zapier keys made and why any failed, and Developer › Webhooks shows each delivery to Zapier. For anything else, contact us.

Questions

Which plans include it?

Available on Starter and above. On the Free plan, creating a key or trigger for Zapier asks you to upgrade first, and a key made for Zapier stops working if your account moves back to the Free plan. Otherwise only your plan’s usual limits apply: contacts, emails (including the lower daily limit for new accounts) and up to 1,000 event names per workspace.

What happens when I turn a Zap off?

Its subscription in Kirora is removed, so Kirora stops sending it events.

Can I see what Zapier is doing?

Yes. The Webhooks page shows the subscriptions Zapier created, and the key’s page shows its recent calls.

Next steps

Webhooks: every event Kirora can send, and how deliveries are signed.
HTTP API: the API behind the actions, for anything a step doesn’t cover.
Connect an integration: the guide in the docs.