> 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/dynamics-add-lead-activity.md).

# Dynamics - Add Lead activity

The Add Lead Activity step creates a Task or Phone Call on a Lead record in Microsoft Dynamics 365 Sales, with no fallback to a Contact if no Lead is found.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-cbdc74f59ebdfe34cc14a9fa1702049dab7896b7%2Fdynamics-add-lead-activity-step-settings.png?alt=media" alt="Add Lead Activity panel with Topic, Description, Activity Type, Owner and schedule"></div>

## Step configuration

When you add this step to a Journey, configure the following fields:

* **Topic (required):** the title of the activity in Dynamics, for example "Follow-up Call" or "Send Pricing Guide".
* **Description:** additional details or notes for the person completing the task.
* **Activity Type:** log the activity as either a Task or a Phone Call.
* **Owner (required):** the Dynamics user assigned to the activity.
* **Schedule:** an optional delay before the activity starts, for example "Schedule to start in 2 days".

## Strict Lead matching

Because this step is designed for Leads, eMarketeer uses a strict search process:

* eMarketeer searches Dynamics exclusively for a matching Lead.
* If a Lead is found, the activity is created and attached to that Lead record.
* If no Lead is found, the step is skipped and no activity is created. eMarketeer does not attempt to find or update a Contact record.


---

# 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/dynamics-add-lead-activity.md?ask=<question>&goal=<user_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.