Per-pair page

Connect Stripe to Mindee in two minutes.

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

Connect Stripe and Mindee See reverse direction

Trigger app

Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →

Action app

Mindee as the action

Workflows do something in Mindee, instantly.

Mindee Predict ReceiptAPI

Both directions

Pick the way that fits your stack.

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

Stripe → Mindee

When something happens in Stripe, do it in Mindee.

10 Stripe triggers wired to 1 Mindee actions. Most-used pairing: Charge Failed → Mindee Predict Receipt.

Mindee → Stripe

Or fire it the other way around.

0 Mindee triggers wired to 31 Stripe actions downstream.

Use any trigger in the catalog as the upstream.

See Mindee → Stripe →

Popular pairings

Common Stripe → Mindee workflows.

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

Showing 3 of 10 combinations

When charge failed in Stripe, mindee predict receipt in Mindee.

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, mindee predict receipt in Mindee.

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, mindee predict receipt in Mindee.

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 Mindee in five steps.

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

1
Connect
Authorize Stripe and Mindee
Open Tiny Command, authorize Stripe and Mindee once each. Both connections are available to every workflow on your account.
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
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
Action
Add the Mindee action
Drop the Mindee → Mindee Predict Receipt action below it. Map fields from the Stripe payload into the Mindee inputs.
mindee.predict-receipt
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 + Mindee.

How long does it take to connect Stripe and Mindee on Tiny Command?

Under two minutes. Authorize Stripe and Mindee once each, drop the Stripe trigger and Mindee action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Stripe ↔ Mindee integration real-time?

Yes. Both Stripe and Mindee 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 Mindee?

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 Mindee.

What Stripe events can trigger a Mindee 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 Mindee?

No. There's a free tier that covers most Stripe+Mindee use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Mindee → Stripe instead?

Build it the same way, in reverse. There's a dedicated /integrations/mindee/with/stripe page with the reverse-direction triggers and actions.

Other apps that pair well with Stripe.

Stripe + Gmail

Stripe + Slack

Communication

Stripe + Google Sheets

Spreadsheets & Databases