> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/dynamics/dynamics-journey-steps/create-update-lead.md).
# Dynamics - Create/Update Lead
The Create/Update Lead step pushes contacts from eMarketeer into your Microsoft Dynamics CRM as Leads, with built-in logic to update existing records and prevent duplicates.
### Step configuration
When you add this step to a Journey, configure the following fields:
* **Topic (required):** Sets the main title for the Lead record in Dynamics (for example, "Webinar Attendee" or "Contact Us Form").
* **Description:** Passes additional notes, campaign details, or context to your sales team.
### The "Always create a lead" setting
This checkbox controls how eMarketeer searches your CRM and handles existing records.
**If unchecked (default)**
This option protects your CRM from creating Leads for people who have already progressed in your sales cycle.
* eMarketeer first checks Dynamics to see if the person already exists as a Contact.
* **If they are a Contact:** The step stops completely. No Lead is created.
* **If they are not a Contact:** eMarketeer updates an existing Lead. If no Lead is found, it creates a new one.
**If checked**
This option forces the step to process the Lead, regardless of whether the person already exists as a Contact in your CRM.
* eMarketeer bypasses the initial Contact check and attempts to update an existing Lead.
* If no existing Lead is found, it creates a new Lead.
* **Smart linking:** If it creates a new Lead *and* the person already exists as a Contact in Dynamics, eMarketeer automatically links the new Lead to their existing Contact and Account records.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.emarketeer.com/integrations/dynamics/dynamics-journey-steps/create-update-lead.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
