> 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/docs/docs_se/integrationer/dynamics/dynamics-journey-steps/dynamics-add-contact-to-marketing-list.md).

# Dynamics - Add Contact to Marketing List

Steget Add Contact to Marketing List lägger till en person i en specifik Marketing List i din Microsoft Dynamics CRM, och riktar sig specifikt mot Contact-poster.

<div align="left" data-with-frame="true"><img src="https://2555292243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FicfGEyRadiE4k7sV4O4o%2Fuploads%2Fgit-blob-c4ca6517458a84931075c660e3114ac80ea14cfc%2FAdd_contact_to_marketing_list-1024x406.png?alt=media" alt="Konfiguration av steget Add Contact to Marketing List i Dynamics"></div>

### Stegkonfiguration

När du lägger till detta steg i en Journey behöver du bara konfigurera ett fält:

* **Marketing List (obligatoriskt):** Välj den Dynamics Marketing List från rullgardinsmenyn där du vill lägga till Contacten.

### Strikt Contact-matchning

Eftersom detta steg är utformat specifikt för Contacts använder eMarketeer en strikt sökprocess:

* eMarketeer söker i Dynamics uteslutande efter en matchande Contact.
* Om en Contact hittas läggs den till i den valda Marketing List.
* **Om ingen Contact hittas:** Steget hoppas över och personen läggs inte till i listan. eMarketeer försöker **inte** att hitta eller lägga till en Lead-post.


---

# 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/docs/docs_se/integrationer/dynamics/dynamics-journey-steps/dynamics-add-contact-to-marketing-list.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.