> 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/smartlead.md). # Smartlead Use Smartlead Add to Campaign to enroll a lead in a configured campaign. ## Connect An admin opens **Settings → Integrations → Smartlead** and enters the API key. Saving reads the campaigns to verify access without changing leads. ## Configure a campaign Choose the campaign and map the prospect email and supported person fields. Place the step after qualification and any suppression conditions your team requires. The step offers **Ignore global block list** and **Ignore unsubscribe list**. Review these deliberately before saving; enabling them bypasses the corresponding provider restriction. ## Check the outcome Inspect the campaign ID, lead ID and status. Verify a controlled live lead in the intended campaign. If a lead is skipped, review the skip reason and suppression policy. If the call fails, check the API key, campaign ID, accepted fields and provider error. Adding a lead to a campaign and sending its first message are separate provider events. A successful workflow result does not establish that the first email has been delivered. A simulated campaign enrollment uses samples. See [Sequence enrollment outcomes](/workflows/sequence-outcomes.md) for handling existing, skipped and failed enrollments. --- # 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/smartlead.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.