Skip to content
Per-pair page

Connect Stripe to Mandrill in two minutes.

Real-time triggers from Stripe, ready-made actions in Mandrill. 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
Mandrill as the action

Workflows do something in Mandrill, instantly.

Both directions

Pick the way that fits your stack.

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

StripeMandrill

When something happens in Stripe, do it in Mandrill.

10 Stripe triggers wired to 4 Mandrill actions. Most-used pairing: Charge FailedGet Mandrill Account Info.

MandrillStripe

Or fire it the other way around.

0 Mandrill triggers wired to 31 Stripe actions downstream.

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

Common Stripe → Mandrill 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, get mandrill account info in Mandrill.

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, list mandrill templates in Mandrill.

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, mandrill send email in Mandrill.

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, mandrill send template email in Mandrill.

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, get mandrill account info in Mandrill.

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, list mandrill templates in Mandrill.

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, mandrill send email in Mandrill.

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, mandrill send template email in Mandrill.

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, get mandrill account info in Mandrill.

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

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

  1. 1
    Connect
    Authorize Stripe and Mandrill

    Open Tiny Command, authorize Stripe and Mandrill 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 Mandrill action

    Drop the Mandrill → Get Mandrill Account Info action below it. Map fields from the Stripe payload into the Mandrill inputs.

    mandrill.get-info
  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 + Mandrill.

How long does it take to connect Stripe and Mandrill on Tiny Command?
Under two minutes. Authorize Stripe and Mandrill once each, drop the Stripe trigger and Mandrill action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Stripe ↔ Mandrill integration real-time?
Yes. Both Stripe and Mandrill 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 Mandrill?
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 Mandrill.
What Stripe events can trigger a Mandrill 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 Mandrill?
No. There's a free tier that covers most Stripe+Mandrill use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Mandrill → Stripe instead?
Build it the same way, in reverse. There's a dedicated /integrations/mandrill/with/stripe page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Stripe.


Wire Stripe to Mandrill in 2 minutes.

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