> 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-contact-activity.md).

# Dynamics - Add contact activity

![Add Contact Activity step configuration in Dynamics](/files/m4XwMSkdEzck3pjdwYX5)

### Step configuration

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

* **Subject (required):** Sets the title of the activity in Dynamics.
* **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").

### Strict Contact matching

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

* eMarketeer searches Dynamics exclusively for a matching Contact.
* If a Contact is found, the activity is created and attached to that Contact record.
* **If no Contact is found:** The step is skipped and no activity is created. eMarketeer does **not** attempt to find or update a Lead 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.emarketeer.com/integrations/dynamics/dynamics-journey-steps/dynamics-add-contact-activity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.