> 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-activity.md). # Dynamics - Add activity The Add Activity step creates a Task or Phone Call in your Microsoft Dynamics CRM, asking for your Lead or Contact preference and using a built-in fallback so the activity is always logged.
Add Activity panel with the Prefer Lead and Prefer Contact options
### Step configuration When you add this step to a Journey, configure the following fields: * **Topic (required):** Sets the title of the activity in Dynamics (for example, "Follow-up Call" or "Send Pricing Guide"). * **Description:** Provides additional details or notes for the person completing the task. * **Activity Type:** Choose whether to log the activity as a **Task** or a **Phone Call**. * **Owner (required):** Select the Dynamics user who will be assigned the activity. * **Schedule:** Optionally set a delay for the activity (for example, "Schedule to start in 2 days"). ### The "Prefer Contact or Lead" setting This setting controls which record type eMarketeer prioritizes when searching Dynamics. If the preferred record type is not found, eMarketeer automatically searches for the alternative so the activity is not lost. **If you select "Prefer Lead"** * eMarketeer first searches Dynamics for a matching Lead. * If a Lead is found, the activity is attached to the Lead. * **Fallback:** If no active Lead is found, eMarketeer automatically searches for a matching Contact. If found, the activity is attached to the Contact. **If you select "Prefer Contact"** * eMarketeer first searches Dynamics for a matching Contact. * If a Contact is found, the activity is attached to the Contact. * **Fallback:** If no Contact is found, eMarketeer automatically searches for a matching Lead. If found, the activity is attached to the Lead. *Note: If eMarketeer cannot find either a Lead or a Contact in Dynamics, the step is skipped and no activity is created.* --- # 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-activity.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.