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

# Dynamics - Add contact activity

Unlike the generic Add Activity step, this action does not fall back to a Lead when a Contact is missing. Use it when the activity must be tied to a Dynamics Contact specifically.

## Step configuration

When you add this step to your journey, you configure the following fields:

* Subject (required): the title of the activity in Dynamics.
* Description: additional details or notes for the person completing the task.
* Activity Type: log the activity as a Task or a Phone Call.
* Owner (required): the Dynamics user assigned to 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 for Contacts, eMarketeer uses a strict search:

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


---

# 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/journey-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.