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

# Dynamics - Add Lead activity

Steget Add Lead Activity skapar en Task eller ett Phone Call på en Lead-post i Microsoft Dynamics 365 Sales, utan fallback till en Contact om ingen Lead hittas.

<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-cbdc74f59ebdfe34cc14a9fa1702049dab7896b7%2Fdynamics-add-lead-activity-step-settings.png?alt=media" alt="Panelen Add Lead Activity med Topic, Description, Activity Type, Owner och schemaläggning"></div>

## Stegkonfiguration

När du lägger till detta steg i en Journey, konfigurera följande fält:

* **Topic (obligatoriskt):** titeln på aktiviteten i Dynamics, till exempel "Follow-up Call" eller "Send Pricing Guide".
* **Description:** ytterligare detaljer eller anteckningar för personen som ska utföra uppgiften.
* **Activity Type:** logga aktiviteten antingen som en Task eller ett Phone Call.
* **Owner (obligatoriskt):** den Dynamics-användare som tilldelas aktiviteten.
* **Schedule:** en valfri fördröjning innan aktiviteten startar, till exempel "Schedule to start in 2 days".

## Strikt Lead-matchning

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

* eMarketeer söker i Dynamics uteslutande efter en matchande Lead.
* Om en Lead hittas skapas aktiviteten och kopplas till den Lead-posten.
* Om ingen Lead hittas hoppas steget över och ingen aktivitet skapas. eMarketeer försöker inte att hitta eller uppdatera en Contact-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-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.