> 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/salesloft.md). # Salesloft Use **Salesloft Start Cadence** to put an eligible person into a cadence. ## Connect An admin opens **Settings → Integrations → Salesloft** and enters the API key. Saving reads the key owner to verify access; it does not change people or cadences. Map member Salesloft identities where the workflow needs a particular sending user. ## Configure a cadence Choose the **Cadence** and map the prospect's email and person fields. Select the **Sending user** if you want one explicitly; otherwise the step defaults to the user who owns the API key. Check the cadence and sender together. The routing assignee does not automatically become the sender unless the configured mapping supplies that user. ## Verify Inspect person, cadence and membership IDs in the result. Make a controlled live test and review the cadence membership in Salesloft. If the step fails, check the API key owner's permissions, cadence access, numeric resource IDs and person data. A skipped membership or existing enrollment should follow its own outcome path. Use [Sequence enrollment outcomes](/workflows/sequence-outcomes.md) to design retries and [Connected identities](/settings/identities.md) to retain the intended sender. --- # 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/salesloft.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.