Skip to content
Per-pair page

Connect Stripe to Kustomer in two minutes.

Real-time triggers from Stripe, ready-made actions in Kustomer. Filter, transform, and route without writing a line of code.

Trigger app
Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →
Action app
Kustomer as the action

Workflows do something in Kustomer, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

StripeKustomer

When something happens in Stripe, do it in Kustomer.

10 Stripe triggers wired to 4 Kustomer actions. Most-used pairing: Charge FailedCreate Kustomer Conversation.

KustomerStripe

Or fire it the other way around.

0 Kustomer triggers wired to 31 Stripe actions downstream.

  • Use any trigger in the catalog as the upstream.
See KustomerStripe
Popular pairings

Common Stripe → Kustomer workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 40 combinations
When charge failed in Stripe, create kustomer conversation in Kustomer.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, create kustomer customer in Kustomer.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, send kustomer message in Kustomer.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, search kustomer customers in Kustomer.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When checkout completed in Stripe, create kustomer conversation in Kustomer.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, create kustomer customer in Kustomer.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, send kustomer message in Kustomer.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, search kustomer customers in Kustomer.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When new customer in Stripe, create kustomer conversation in Kustomer.

Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.

How it works

Connect Stripe and Kustomer in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Stripe and Kustomer

    Open Tiny Command, authorize Stripe and Kustomer once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Stripe trigger

    Drop the Stripe → Charge Failed trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/stripe.trigger-charge-failed
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Kustomer action

    Drop the Kustomer → Create Kustomer Conversation action below it. Map fields from the Stripe payload into the Kustomer inputs.

    kustomer.create-conversation
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Stripe + Kustomer.

How long does it take to connect Stripe and Kustomer on Tiny Command?
Under two minutes. Authorize Stripe and Kustomer once each, drop the Stripe trigger and Kustomer action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Stripe ↔ Kustomer integration real-time?
Yes. Both Stripe and Kustomer expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Stripe and Kustomer?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Kustomer.
What Stripe events can trigger a Kustomer workflow?
Any of the 10 Stripe triggers, including "Charge Failed". Each fires in real time when the matching event happens in Stripe.
Do I need a paid plan to use Stripe with Kustomer?
No. There's a free tier that covers most Stripe+Kustomer use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Kustomer → Stripe instead?
Build it the same way, in reverse. There's a dedicated /integrations/kustomer/with/stripe page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Stripe.


Wire Stripe to Kustomer in 2 minutes.

Free tier available. No credit card. No onboarding call.