Skip to content
EmailReal-timeUpdated May 2026
M

Microsoft Dynamics 365

Dynamics 365 CRM records into your stack

Microsoft Dynamics 365 is the enterprise CRM choice for organizations already standardized on Microsoft 365, the connector lets teams wire it into workflows without writing Power Automate. Two triggers cover the broad event surface: Record Created and Record Updated. Both fire on any object type the connected user has access to (Account, Contact, Lead, Opportunity, Task, Custom Entity), with the record type identified in the payload so a workflow can branch by object. Nine actions cover the operational side: Create Account, Create Contact, Create Opportunity, Create Task, Update Account, Get Contact, List Opportunities, Search Contacts, plus the related read endpoints. Authorize via Azure AD OAuth (the connector handles the consent flow). The connection respects Dynamics 365 security roles, workflows can only read or write what the authorized user has permission to do. Common patterns: an Opportunity Created event with stage equals Qualification fans into a Notion CS prep doc and a Slack channel; or a Lead Created with a high lead-score fires an outreach workflow.

2triggers
9actions
≈ 2 minto set up
Freetier · no card
Triggers

Workflows start when Microsoft Dynamics 365 does.

2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven
Actions

Do anything Microsoft Dynamics 365 can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it does
Create Dynamics AccountCreates a company/account record in Dynamics with name, industry, custom fields. For "new B2B prospect → account record before contact" workflows.
Create Dynamics ContactCreates a contact tied to an account with email, name, custom fields. For "form submission → push to Dynamics" sync workflows.
Create Dynamics OpportunityCreates a sales opportunity with estimated value, close date, owner. For "qualified lead → auto-create opportunity in the right pipeline" workflows.
Create Dynamics TaskCreates a follow-up task tied to a contact, account, or opportunity. For "deal stagnant → create follow-up task" or "support ticket needs review → assign as task" patterns.
Get Dynamics ContactReturns a contact by ID with all standard and custom fields plus related account, opportunities, activities. The standard lookup before update or for enrichment workflows.
List Dynamics OpportunitiesPaginated opportunities with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or owner.
Search Dynamics ContactsLookup by name, email, or other field. The standard "find before update" pattern for upsert workflows.
Update Dynamics AccountPartial update on account fields. For "enrichment from external source → write back to Dynamics" sync patterns.
Update Dynamics ContactPartial contact update. For "Clearbit enriched this contact → push to Dynamics" or "support tagged contact → reflect in CRM" workflows.
Recipes

Pre-built Microsoft Dynamics 365 workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Microsoft Dynamics 365 once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Microsoft Dynamics 365 field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Microsoft Dynamics 365 integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Microsoft Dynamics 365 to Tiny Command?
Open the Tiny Command workflow builder, drop in a Microsoft Dynamics 365 node, and click Connect. Authorize Microsoft Dynamics 365 once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What Microsoft Dynamics 365 triggers does Tiny Command support?
Tiny Command supports 2 real-time Microsoft Dynamics 365 triggers, including "Dynamics Record Created", "Dynamics Record Updated". Each trigger fires within seconds of the event happening in Microsoft Dynamics 365.
What Microsoft Dynamics 365 actions can I run from a workflow?
9 Microsoft Dynamics 365 actions are available out of the box, covering email operations like "Create Dynamics Account". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the Microsoft Dynamics 365 integration real-time?
Yes. Dynamics Record Created and every other Microsoft Dynamics 365 trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Microsoft Dynamics 365 rather than on a polling schedule.
Do I need to write code to use Microsoft Dynamics 365 with Tiny Command?
No. Every Microsoft Dynamics 365 trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Microsoft Dynamics 365 API endpoint directly.
How much does the Microsoft Dynamics 365 integration cost?
There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Microsoft Dynamics 365 integration itself has no per-app surcharge.
Related

More email apps people connect.

Same category as Microsoft Dynamics 365, ordered by how often teams pair them. Hover the carousel to pause.

Do more with Microsoft Dynamics 365.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.