> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.default.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Smartlead integration in Default

> How to connect Smartlead to Default with an API key and add leads to Smartlead campaigns from workflows with the Add to Smartlead Campaign node, including the lead fields Default sends and how it reports skipped leads.

Smartlead is a native sequencing integration in Default. An admin connects Smartlead once with a
Smartlead API key, and workflows then add leads to Smartlead campaigns with the
**Add to Smartlead Campaign** node. Smartlead sends the emails. Default has no sequencing product of
its own.

<Note>
  Select **Settings** in the sidebar, then **Integrations** under **Workspace Settings**, and open
  **Smartlead**. Admin access is required.
</Note>

## What Default can do with Smartlead

| Capability | Supported |
| - | - |
| Add a lead to a Smartlead campaign from a workflow | Yes, with the **Add to Smartlead Campaign** node |
| Pick the campaign | Yes. Active, paused, and drafted campaigns appear in the picker. Stopped, archived, and completed campaigns do not. |
| Set standard lead fields and custom fields on the lead | Yes, with **Lead fields** |
| Override Smartlead's duplicate, block list, unsubscribe, and bounce checks | Yes, per node |
| Pick the sending mailbox for each lead | No. The campaign's own email account rotation picks the sender. |
| Read replies, opens, or lead status back from Smartlead | No |
| Remove a lead from a campaign, or pause a lead | No |

## Connect Smartlead to Default

Smartlead connects with an API key rather than a sign-in popup.

<Steps>
  <Step title="Get an API key">
    In Smartlead, generate an API key under **Settings** → **API Keys**.
  </Step>

  <Step title="Open the Smartlead card">
    Select the Smartlead card on the **Integrations** page to open its detail page.
  </Step>

  <Step title="Enter the key in Default">
    Select **Connect**. In the **Connect to Smartlead** dialog, paste the key into **API Key** and
    select **Connect**. Default stores the key and uses it for every Smartlead request from your
    workspace. Smartlead is connected, and the card's **Connect** button now reads **Manage**.
  </Step>
</Steps>

Select **Disconnect** on the detail page to remove Smartlead.

Mapping each member to a Smartlead email account is optional, and Default does not do it
automatically. In **Settings** → **Users**, fill in the member's cell in the **Smartlead** column of
the **Mappings** tab. You can also open the member, select **Integrations**, and set
**Email Account** on the Smartlead card. See [Users](/settings/users). The
**Add to Smartlead Campaign** node does not use this mapping to pick a sender, because Smartlead's
campaign rotation picks it.

## Add a lead to a Smartlead campaign

Add the **Add to Smartlead Campaign** node from the **Sequencing** section of **Add Node**. The node
appears only while Smartlead is connected. Each run adds 1 lead.

| Field | What it does |
| - | - |
| **Campaign** | The Smartlead campaign to add the lead to. The picker marks drafted and paused campaigns. Activate a drafted campaign in Smartlead before the workflow goes live. |
| **Email** | The lead's email address, from the trigger or an earlier node. Required. Smartlead identifies leads by email only. |
| **Lead fields** | Optional values to set on the lead. See [Lead fields Default sends](#lead-fields-default-sends-to-smartlead). |
| **Allow leads in other campaigns** | Adds the lead even if it already exists in another campaign on the account. Off by default. |
| **Ignore global block list** | Adds the lead even if its email or domain is on the account-wide block list. Off by default. |
| **Ignore unsubscribe list** | Adds the lead even if it unsubscribed from your campaigns before. Off by default. |
| **Ignore community bounce list** | Adds the lead even if its email bounced in other Smartlead customers' campaigns. Off by default. |

For the node in the context of other sequencing tools, see
[Sequencing nodes](/workflows/steps-sequencing#add-to-smartlead-campaign).

<Warning>
  A workflow test runs this node for real. The lead is added to the campaign, and Smartlead can start
  sending on the campaign's schedule. Use a test email address.
</Warning>

## Lead fields Default sends to Smartlead

**Lead fields** suggests the standard Smartlead fields. Default sends these at the top level of the
lead:

| Label | Smartlead field |
| - | - |
| **First name** | `first_name` |
| **Last name** | `last_name` |
| **Company name** | `company_name` |
| **Phone number** | `phone_number` |
| **Website** | `website` |
| **Location** | `location` |
| **LinkedIn profile** | `linkedin_profile` |
| **Company URL** | `company_url` |

* Any other key you type becomes a Smartlead custom field on the lead, for example `rep_name` for a
  value your Smartlead templates use. A lead can have up to 200 custom fields.
* A list value is sent as 1 comma-separated string.
* An empty standard field is left out.
* A LinkedIn URL can go in `linkedin_profile`, but it cannot identify the lead. **Email** is always
  required.

## Smartlead results later nodes can use

The node does not stop the workflow when Smartlead skips or rejects the lead. It reports the result,
so a [**Multi-Branch**](/workflows/steps-logic-timing#multi-branch) node can act on it.

| Output | What it holds |
| - | - |
| `success` | `true` when Smartlead added the lead. |
| `leadId` | The Smartlead lead ID, when Smartlead returns it. |
| `addedCount` / `skippedCount` | How many leads Smartlead added or skipped (0 or 1). |
| `skipReason` | Why the lead was likely skipped: `duplicate`, `block_list_or_unsubscribe`, or `unknown`. |
| `error` | The message from Smartlead or Default when the lead was not added. |
| `campaignId` / `email` | The campaign and email the node used. |

Smartlead does not say why it skipped a lead, so Default infers `skipReason` from the toggles you left
off. With **Allow leads in other campaigns** off, a skip reads as `duplicate`.

## Troubleshoot Smartlead in Default

| What you see | What to check |
| - | - |
| **Add to Smartlead Campaign** is missing from **Add Node** | Connect Smartlead in **Settings** → **Integrations**. |
| A campaign is missing from **Campaign** | Stopped, archived, and completed campaigns are hidden. Pick an active, paused, or drafted campaign. |
| Smartlead rejected the request (invalid API key) | Reconnect Smartlead with a current API key. |
| Smartlead could not find the campaign | The campaign was deleted, or the API key's account cannot see it. Pick another campaign. |
| The lead is already enrolled in another Smartlead campaign | Turn on **Allow leads in other campaigns**, or leave it off to keep leads in 1 campaign. |
| The lead is on the block list, unsubscribe list, or community bounce list | Turn on the matching **Ignore** toggle only if you are sure the lead should get email. |
| Smartlead is rate-limiting requests | Smartlead limited requests from your account, and the lead was not added. Add it again after the limit resets. |

To see what the node sent and got back, open the workflow, select **Runs** in the top Context Bar,
and select a run. See [Run logs](/workflows/run-logs).

Related: [Default integrations](https://www.default.com/integrations)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.