Skip to content
MPer-pair page

Connect Stripe to Microsoft Dynamics 365 in two minutes.

Real-time triggers from Stripe, ready-made actions in Microsoft Dynamics 365. 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 →
M
Action app
Microsoft Dynamics 365 as the action

Workflows do something in Microsoft Dynamics 365, instantly.

See all 9 actions →
Both directions

Pick the way that fits your stack.

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

MStripeMicrosoft Dynamics 365

When something happens in Stripe, do it in Microsoft Dynamics 365.

10 Stripe triggers wired to 9 Microsoft Dynamics 365 actions. Most-used pairing: Charge FailedCreate Dynamics Account.

MMicrosoft Dynamics 365Stripe

Or fire it the other way around.

2 Microsoft Dynamics 365 triggers wired to 31 Stripe actions downstream.

See Microsoft Dynamics 365Stripe
Popular pairings

Common Stripe → Microsoft Dynamics 365 workflows.

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

Showing 9 of 90 combinations
M
When charge failed in Stripe, create dynamics account in Microsoft Dynamics 365.

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

M
When charge failed in Stripe, create dynamics contact in Microsoft Dynamics 365.

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

M
When charge failed in Stripe, create dynamics opportunity in Microsoft Dynamics 365.

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

M
When charge failed in Stripe, create dynamics task in Microsoft Dynamics 365.

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

M
When checkout completed in Stripe, create dynamics account in Microsoft Dynamics 365.

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

M
When checkout completed in Stripe, create dynamics contact in Microsoft Dynamics 365.

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

M
When checkout completed in Stripe, create dynamics opportunity in Microsoft Dynamics 365.

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

M
When checkout completed in Stripe, create dynamics task in Microsoft Dynamics 365.

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

M
When new customer in Stripe, create dynamics account in Microsoft Dynamics 365.

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 Microsoft Dynamics 365 in five steps.

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

  1. 1
    Connect
    Authorize Stripe and Microsoft Dynamics 365

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

    Drop the Microsoft Dynamics 365 → Create Dynamics Account action below it. Map fields from the Stripe payload into the Microsoft Dynamics 365 inputs.

    microsoft-dynamics-365.create-account
  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 + Microsoft Dynamics 365.

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

Other apps that pair well with Stripe.


Wire Stripe to Microsoft Dynamics 365 in 2 minutes.

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