Kirora is coming. Email and push first. WhatsApp and SMS to follow.Join the waitlist
Integrations

Plug Kirora into the tools you already use.

Connect your customer data to the messages you send. Bring contacts and events in from your backend, payment provider or CSV, then send delivery and engagement events back to your systems through signed webhooks.

What’s included

Keep customer data moving and connections visible.

  • One place for every connection

    An Integrations area lists each one as connected, not connected or failing, with its last activity and the last problem in plain words.

  • A key per source

    Every app, environment or tool gets its own API key, so traffic can be traced and one source revoked without touching the rest.

  • A log of what came in

    See each source’s recent calls, with status and the reason anything failed. Payloads aren’t stored, because they hold contact data.

  • Webhooks out, signed

    Subscribe any HTTPS endpoint to the events you choose. Deliveries are signed, retried, and paused if an endpoint keeps failing.

  • Standard commerce events

    Payments and stores all speak the same “Order Completed”, so one journey works whichever tool the order came from.

  • Use each connection across the platform

    Incoming contacts and events use the same data model. Build segments, trigger journeys and measure goals without creating a separate workflow for each source.

Directory

Explore integrations and upcoming connectors.

  • At launch

    Stripe

    Connect your Stripe account to turn successful payments into purchase events for journeys and revenue reports.

    PaymentsData in
  • At launch

    Paystack

    Successful charges arrive as “Order Completed” events with the amount, ready for journeys and revenue reports.

    PaymentsData in
  • At launch

    HTTP API

    Identify contacts and track events from your backend, with a key made for each source.

    DeveloperData inDetails
  • At launch

    Webhooks

    Signed, retried deliveries for messages, contacts, forms, campaigns and journeys. Subscribe from the app or the API.

    DeveloperData outDetails
  • At launch

    Tracking compatibility

    Point the identify and track calls you already send from another platform at Kirora, and run both while you switch. Opt-outs carry over; opt-ins never do.

    MigrationData inDetails
  • At launch

    MCP server and CLI

    Connect an AI assistant through MCP or use the preview CLI. Restricted agent keys can read and draft; your team authorises sends.

    AI agentsIn and outDetails
  • At launch

    CSV import

    Bring contacts from a spreadsheet or another tool, with column mapping and consent.

    DataData inDetails
  • Coming soon

    Zapier

    Create contacts and track events from thousands of apps. The native connector is coming soon.

    AutomationIn and out
  • Coming soon

    Make

    Connect your apps to Kirora with actions and triggers in Make scenarios.

    AutomationIn and out
  • Coming soon

    n8n

    Connect from n8n workflows over the same API and webhooks.

    AutomationIn and out
  • Coming soon

    WooCommerce

    Orders and customers from your store as standard commerce events.

    CommerceData in
  • Coming soon

    Shopify

    Orders and customers from your Shopify store.

    CommerceData in
  • Don’t see your tool?

    Anything that can make an HTTP call can send Kirora contacts and events, and an HTTPS endpoint can receive Kirora’s signed webhooks.

    Build it on the API

Make your next customer message count.

Join the waitlist for launch updates. Bring campaigns, journeys and transactional messages together when Kirora opens.

Kirora is for permission-based email and push. See our Acceptable Use Policy, Terms and Privacy Policy.