Real-time triggers from Stripe, ready-made actions in Microsoft Dynamics 365. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Stripe.
Workflows do something in Microsoft Dynamics 365, instantly.
Pair pages are mirrored. Each direction gets its own dedicated page.
10 Stripe triggers wired to 9 Microsoft Dynamics 365 actions. Most-used pairing: Charge Failed → Create Dynamics Account.
2 Microsoft Dynamics 365 triggers wired to 31 Stripe actions downstream.
See Microsoft Dynamics 365 → Stripe →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 charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
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 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 Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
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 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 Tiny Command, authorize Stripe and Microsoft Dynamics 365 once each. Both connections are available to every workflow on your account.
Drop the Stripe → Charge Failed trigger onto the canvas. Tiny Command auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the Microsoft Dynamics 365 → Create Dynamics Account action below it. Map fields from the Stripe payload into the Microsoft Dynamics 365 inputs.
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Free tier available. No credit card. No onboarding call.