Select Settings in the sidebar, then Integrations under Workspace Settings, and open
Smartlead. Admin access is required.
What Default can do with Smartlead
Connect Smartlead to Default
Smartlead connects with an API key rather than a sign-in popup.1
Get an API key
In Smartlead, generate an API key under Settings → API Keys.
2
Open the Smartlead card
Select the Smartlead card on the Integrations page to open its detail page.
3
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.
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.
For the node in the context of other sequencing tools, see
Sequencing nodes.
Lead fields Default sends to Smartlead
Lead fields suggests the standard Smartlead fields. Default sends these at the top level of the lead:- Any other key you type becomes a Smartlead custom field on the lead, for example
rep_namefor 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 node can act on it.
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
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.
Related: Default integrations