Real-time triggers from Stripe, ready-made actions in Elasticsearch. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Stripe.
Workflows do something in Elasticsearch, instantly.
Pair pages are mirrored. Each direction gets its own dedicated page.
10 Stripe triggers wired to 1 Elasticsearch actions. Most-used pairing: Charge Failed → Index Document.
0 Elasticsearch triggers wired to 31 Stripe actions downstream.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
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.
No code, no glue, no half-day setup. Each step is one click.
Open TinyCommand, authorize Stripe and Elasticsearch once each. Both connections are available to every workflow on your account.
Drop the Stripe → Charge Failed trigger onto the canvas. TinyCommand auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the Elasticsearch → Index Document action below it. Map fields from the Stripe payload into the Elasticsearch inputs.
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
