> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/workflows/nodes/destinations/salesloft.md).

# Salesloft

The **Salesloft Node** allows you to automatically send contacts from your workflow into a **Salesloft cadence**. This is ideal for triggering timely outbound sequences based on enriched data, engagement signals, or lead qualification logic.

It’s your shortcut from data to action — without needing a rep to manually add leads into a sequence.

***

### When to Use It

Use the Salesloft node when you want to:

* Automatically enroll contacts into a predefined Salesloft cadence
* Route contacts to the right cadence based on segmentation or buyer persona

### Configuration Overview

Here’s what you’ll configure:

**Cadence Name**

This dropdown shows available cadences you’ve already built in Salesloft. Select the one you want the contacts to be enrolled in.

<figure><img src="/files/pf6qK7UD5ezNnbRBmLei" alt="" width="375"><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hockeystack.com/account-intelligence/workflows/nodes/destinations/salesloft.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.