Dynamics 365 from Microsoft combines CRM, ERP, and productivity apps to streamline sales, marketing, customer service, and operations in one integrated platform
Dynamics 365 from Microsoft combines CRM, ERP, and productivity apps to streamline sales, marketing, customer service, and operations in one integrated platform On Nagent, Dynamics 365 is exposed as a fully-configurable crm integration that any agent can call — 16 actions, and OAuth authentication. No code is required to wire Dynamics 365 into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Dynamics 365 to automate the kinds of tasks crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Dynamics 365 into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Dynamics 365, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DYNAMICS365_DYNAMICSCRM_CREATE_ACCOUNTCreates a new account entity record in Dynamics CRM using the Web API.
Input parameters
The name of the new account to be created.
The revenue associated with the account.
The user's ID or 'me' for the authenticated user.
A description of the account.
Indicates whether the account is on credit hold.
The category code of the account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_CASECreates a new case (incident) entity record in Dynamics CRM using the Web API.
Input parameters
The subject or title of the case.
The user's ID or 'me' for the authenticated user.
A reference to the related account. Format: '/accounts(GUID)'
A reference to the related contact. Format: '/contacts(GUID)'
A detailed description of the issue or inquiry.
The priority level of the case (e.g., 1 for Low, 2 for Normal, 3 for High).
The source of the case. Valid values: 1 (Phone), 2 (Email), 3 (Web).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_CONTACTCreates a new contact entity record in Dynamics CRM using the Web API.
Input parameters
The user's ID or 'me' for the authenticated user.
The job title of the contact.
The last name of the contact.
The first name of the contact.
The primary telephone number of the contact.
The mobile phone number of the contact.
The city of the contact's address.
The primary email address of the contact.
The country of the contact's address.
The postal code of the contact's address.
The state or province of the contact's address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_INVOICECreates a new invoice entity record in Dynamics CRM using the Web API.
Input parameters
The name or number of the invoice.
The user's ID or 'me' for the authenticated user.
A reference to the related account. Format: '/accounts(GUID)'
A reference to the currency for the transaction. Format: '/transactioncurrencies(GUID)'
A description of the invoice.
A reference to the price list. Format: '/pricelevels(GUID)'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_LEADCreates a new lead entity record in Dynamics CRM using the Web API.
Input parameters
A brief description or title for the lead.
The user's ID or 'me' for the authenticated user. Set explicitly when creating leads on behalf of other users in multi-user or automated workflows.
The last name of the lead.
The first name of the lead.
The primary telephone number of the lead.
The company name associated with the lead. May be enforced as required by some CRM configurations; omitting it can cause the request to be rejected.
The primary email address of the lead.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_OPPORTUNITYCreates a new opportunity entity record in Dynamics CRM using the Web API. Some CRM configurations enforce `estimatedclosedate` and a transaction currency at the server level even though they are schema-optional; omitting them may cause the request to be rejected.
Input parameters
The name or title of the opportunity. This is a required field.
A brief description of the opportunity.
The anticipated revenue from the opportunity.
The expected close date of the opportunity in 'YYYY-MM-DD' format.
The GUID of the related account (without curly braces). Optional.
The GUID of the related contact (without curly braces). Optional.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_CREATE_SALES_ORDERCreates a new sales order entity record in Dynamics CRM using the Web API.
Input parameters
The name of the sales order.
The user's ID or 'me' for the authenticated user.
A reference to the related account. Format: '/accounts(GUID)'
A reference to the currency for the transaction. Format: '/transactioncurrencies(GUID)'
A description of the sales order.
A reference to the price list. Format: '/pricelevels(GUID)'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_GET_A_INVOICEDynamicscrm get a invoice
Input parameters
The ID of the invoice to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_GET_A_LEADDynamicscrm get a lead
Input parameters
The ID of the lead to retrieve (GUID format) Use the value exactly as returned by Dynamics CRM tools — do not reformat or truncate.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_GET_ALL_LEADSDynamicscrm get all leads
Input parameters
Maximum number of leads to return
Number of leads to skip for pagination
OData filter criteria for leads (e.g., contains(fullname,'John')) Date filters require ISO 8601 format (e.g., createdon gt 2024-01-01T00:00:00Z).
Comma-separated list of fields to return (e.g., fullname,emailaddress1)
Field to order by (e.g., createdon desc)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_UPDATE_CASEUpdates an existing case (incident) entity record in Dynamics CRM using the Web API.
Input parameters
The subject or title of the case.
The unique identifier (GUID) of the case to update.
The user's ID or 'me' for the authenticated user.
The current status of the case (e.g., 1 for Active, 2 for In Progress, 3 for Resolved).
A detailed description of the issue or inquiry.
The priority level of the case (e.g., 1 for High, 2 for Normal, 3 for Low).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_UPDATE_INVOICEUpdates an existing invoice entity record in Dynamics CRM using the Web API.
Input parameters
The updated name or number of the invoice.
The updated due date for the invoice in YYYY-MM-DD format.
The user's ID or 'me' for the authenticated user.
The unique identifier (GUID) of the invoice to update.
The updated description of the invoice.
The updated total amount for the invoice.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_UPDATE_LEADUpdates an existing lead entity record in Dynamics CRM using the Web API.
Input parameters
The unique identifier (GUID) of the lead to update. Must be passed exactly as returned by Dynamics CRM lookup tools — no added braces or modified dash formatting.
A brief description or title for the lead.
The user's ID or 'me' for the authenticated user.
Last name of the lead.
First name of the lead.
Primary phone number of the lead.
Name of the company associated with the lead.
Primary email address of the lead.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_UPDATE_OPPORTUNITYUpdates an existing opportunity entity record in Dynamics CRM using the Web API. Some updates may be rejected if required relational fields (e.g., transactioncurrency) are absent from the record, even though they are not exposed as explicit parameters.
Input parameters
The name or title of the opportunity.
The user's ID or 'me' for the authenticated user.
A brief description of the opportunity.
The anticipated revenue from the opportunity.
The unique identifier (GUID) of the opportunity to update. Use the GUID exactly as returned by CRM lookup or list tools — reformatting the value will cause the update to fail.
The current sales stage (e.g., 1 for Qualify, 2 for Develop, 3 for Propose).
The expected close date of the opportunity in 'YYYY-MM-DD' format.
The rating of the opportunity (e.g., 1 for Cold, 2 for Warm, 3 for Hot).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_DYNAMICSCRM_UPDATE_SALES_ORDERUpdates an existing sales order entity record in Dynamics CRM using the Web API.
Input parameters
The updated name of the sales order.
The user's ID or 'me' for the authenticated user.
The updated description of the sales order.
The updated freight or shipping cost for the order.
The unique identifier (GUID) of the sales order to update.
The updated discount amount for the order.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DYNAMICS365_GET_ALL_INVOICES_ACTIONGet all invoices action
Input parameters
Maximum number of invoices to return
Number of invoices to skip for pagination
OData filter criteria for invoices (e.g., contains(customerName,'Contoso'))
Comma-separated list of fields to return (e.g., invoiceid,name,totalamount)
Field to order by (e.g., createdon desc)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 38 agents privately built on Nagent that already use Dynamics 365.
Build on Nagent
Connect Dynamics 365 to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Dynamics 365, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Dynamics 365 is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Dynamics 365 is connected, you configure its 16 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Dynamics 365 steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Dynamics 365 event fires, the agent kicks off automatically.
Every Dynamics 365 action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Dynamics 365 ships with 16 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Dynamics 365 together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Dynamics 365-based workflows tailored to your business.