> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/loops.md). # Loops Use the Loops workflow action to create a marketing contact with fields from the lead journey. ## Connect An admin opens **Settings → Integrations → Loops** and enters the Loops API key. Saving checks the key and team information without creating or changing a contact. ## Create a contact Add the Loops action after the lead identity and eligibility checks. Map the email and supported contact fields using the step's picker. Place the action on the branch whose audience should enter Loops. For example, a newsletter request can enter a marketing path while a booked sales demo follows a separate owner notification path. Make subscription and audience decisions explicitly in your source and workflow. Do not infer marketing permission from the mere presence of an email address. ## Verify Inspect one controlled live contact in Loops and confirm its fields. Simulation uses a sample response. If the step fails, check the API key, destination team, email format and provider error. A connection check confirms the key; it does not establish that every contact field is accepted. Use [Workflow logs](/workflows/logs.md) to distinguish a failed contact operation from a later notification failure. An earlier successful external write remains relevant when troubleshooting the rest of a run. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/loops.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 `build a script that syncs our docs to a CMS` 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.