Integrations connect Kirora to your existing systems. Bring contacts and events in, then send updates back through webhooks. A payment provider such as Stripe can turn successful payments into Order Completed events for segments, journeys and revenue reports.
The Integrations page
Go to Integrations to see every integration and its status in this workspace:
- Connected: working and receiving data.
- Not connected: available but not set up.
- Failing: something went wrong recently. Open it to see the last problem in plain words.
Integrations connect the whole workspace, so only admins and owners can see this page, and only the owner can connect a payment provider.
Connect Stripe
- In Stripe, go to Developers › API keys and copy your secret key (it starts
sk_), or create a restricted key that can read charges and manage webhook endpoints. - In Kirora, go to Integrations › Stripe.
- Paste it into Secret key and choose Connect Stripe.
Kirora checks the key and sets up the connection in your Stripe account for you, so there’s nothing to paste back into Stripe.
Connect Paystack
- In Paystack, go to Settings › API Keys & Webhooks and copy your secret key.
- In Kirora, go to Integrations › Paystack, paste it into Secret key and choose Connect Paystack.
- Choose Copy webhook URL.
- Back in Paystack’s Settings › API Keys & Webhooks, paste it as the webhook URL for the same mode as your key (live or test).
Until Paystack knows where to send payments, nothing arrives. The page shows Last payment received so you can check it’s working.
What a connected payment provider does
- Each successful payment becomes an Order Completed event on the customer who paid, matched by email address, with the amount and currency.
- A payer who isn’t a contact yet is added without marketing consent, so your marketing email only reaches people who agreed to it.
- The same payment is never counted twice.
Use these events to:
- Start a journey with a thank-you or a review request after an order. See Build a journey.
- Build a segment of customers who ordered recently, or haven’t ordered in 60 days. See Segments.
- Credit campaigns with revenue through a conversion goal. See Reports.
To change keys, choose Replace key. To stop, choose Disconnect. Events already recorded stay.
Other integrations
| Integration | Status |
|---|---|
| Stripe, Paystack | Available now |
| CSV import | Available now. See Import contacts |
| HTTP API | Available now, for your developers |
| Webhooks | Available now, for your developers |
| Claude, Cursor and other AI assistants | Available now. See Use Kiro AI with Claude or Cursor |
| Zapier, Make, n8n | Kirora’s own apps are coming soon |
| Shopify, WooCommerce | Coming soon |
Until the Zapier, Make and n8n apps arrive, someone comfortable with those tools can already connect them: each integration’s page in Kirora lists the steps to create a key and send contacts and events through the tool’s own web request step.
For your developers
The HTTP API lets your website or app add contacts and record events such as sign-ups or bookings. Webhooks send Kirora’s events, such as deliveries, unsubscribes and form signups, to your own systems. Each source gets its own key, and its page shows Recent calls so problems are easy to trace. Point your developer to the API quickstart and the webhooks guide.