Smartlead is a cold email outreach platform for running multi-step email campaigns from many sender mailboxes, with mailbox warmup, a unified inbox for replies, deliverability testing, and agency client management. The Smartlead connector reads campaigns, leads, sequences, email accounts, campaign and account analytics, inbox conversations, webhooks, clients, Smart Delivery spam tests, Smart Prospect searches, and Smart Senders and SmartServers data, and can create and manage campaigns, leads, lead lists, email accounts, webhooks, and clients, start campaigns, and send replies and emails.
Power end-to-end data operations for your Smartlead API with Nexla. Our bi-directional Smartlead connector is purpose-built for Smartlead, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Smartlead or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Smartlead workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
In the API key section, generate a new API key, and copy it. Store the key securely; Smartlead may not show it again.
For details, see Smartlead's Authentication guide. The API key carries the same access as your Smartlead account, so treat it like a password. Every Smartlead request authenticates with the key in the api_key query parameter; Nexla adds this parameter to each request automatically, so do not add it to endpoint URLs yourself.
Smart Delivery, Smart Prospect, Smart Senders, and SmartServers are separate Smartlead products. The templates for them only work if the product (or add-on) is enabled on your Smartlead account, and they can fail with an authorization error otherwise.
Some destinations send real email
Several Smartlead destination templates cause Smartlead to send email to real recipients: starting or resuming a campaign, adding or pushing leads into an active campaign, resuming a lead, attaching mailboxes to an active campaign, saving sequences on an active campaign, replying to or forwarding an email, sending a single or test email, enabling warmup, and creating placement tests. These templates are marked Sends email below. Test them against a draft or paused campaign and your own addresses before using them with live data.
Some Smart Prospect templates spend credits
The Find Emails API and Fetch Contacts API destination templates reveal contact email addresses and spend Smart Prospect credits on your Smartlead account for every record they send. These templates are marked Spends credits below. Check your credit balance with the Search Analytics API source template before running them.
Smartlead API rate limits
Smartlead rate-limits each API key across all endpoints, by plan (for example, 60 requests per minute on the Standard tier), and returns HTTP 429 Too Many Requests when the limit is exceeded. Three endpoints have their own, stricter limit of 10 requests per minute per account: campaign lead statistics, all leads activities, and domain-wise health metrics. Templates that page through large result sets make one request per page. See Smartlead's Rate Limits guide for details.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Smartlead API key in the API Key field. This is the key you created in Prerequisites. Nexla sends it as the api_key query parameter on every request to every Smartlead host.
If your API key is compromised, generate a new key in Smartlead under Settings, and update the API Key on this credential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by listing the campaigns in your Smartlead account.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Smartlead connector tile, then select the credential that will be used to connect to your Smartlead account, and click Next; or, create a new Smartlead credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Smartlead endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Templates that say "Results are paged automatically" read every page, advancing the offset by the page size until a page comes back short; all other templates make a single request. Templates that need an ID, such as a campaign or email account ID, read data for that one object; use the matching list template to find the ID. Templates with a date range default to the last 30 days.
Lists every campaign in the account, newest first, with each campaign's ID, name, status, schedule, tracking settings, and sending limits. Use it to find the campaign IDs that most other templates need.
Lists email-level statistics for every email sent in a campaign, including each email's lead, sequence number, and sent, open, click, reply, and bounce times.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Results are paged automatically, 1,000 records per page.
Returns per-sequence and per-variant performance for a campaign over a date range, with open, click, and reply rates.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns a campaign's high-level metrics for a date range.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Searches a campaign's leads. As configured, the template sends an empty filter and returns the first page of the campaign's leads; to filter by name or email text, status, category, or sequence, use manual configuration with the filters Smartlead documents.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Retrieves message history for many leads of a campaign at once. As configured, the template sends an empty request body, so it does not narrow the result to particular leads.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Returns account-wide sent, opened, clicked, replied, and bounced totals for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns performance for each campaign over a date range, with engagement rates and lead counts.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns a response analysis for each campaign over a date range, with a sentiment breakdown.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns reply rates for follow-up steps (second, third, and later emails) over a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns the average time from first email sent to first reply received, over a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns the average number of leads contacted before the first reply, over a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns day-by-day email engagement metrics for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns day-by-day engagement metrics grouped by the time emails were sent, for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns day-by-day positive reply counts (interested and other positive categories) for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns day-by-day positive replies grouped by the time emails were sent, for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns lead engagement statistics by status and category for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns lead responses broken down by category for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns mailbox performance aggregated by sending domain, for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Smartlead limits this endpoint to 10 requests per minute per account, separately from the plan-wide limit.
Returns health metrics for each email account, for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Compares performance across email providers (such as Gmail, Outlook, and SMTP) for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns performance metrics by team member for a date range.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Returns performance metrics for each client over a date range, for agency reporting.
Start Date and End Date default to {now-30} and {now}, the last 30 days, and are sent as yyyy-MM-dd. Replace them with other date macros or fixed dates to change the range.
Enter the Master Inbox ID. This is the lead's campaign_lead_map_id, as returned by the inbox and campaign lead templates (for example, Get Inbox Replies).
Returns a summary of a campaign's webhook deliveries, such as successful and failed events, for a time range.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
From Time and To Time default to {now-30} and {now}, the last 30 days, and are sent as UTC timestamps (for example, 2026-01-31T00:00:00.000Z). Replace them with other date macros or fixed dates to change the range.
Searches Smartlead's prospect database for contacts that match your filters. Contacts are returned as found; revealing their email addresses is a separate, credit-consuming step (see Fetch Contacts API and Find Emails API under destinations).
Enter the complete JSON request body in Search Body, with any of the filters that Smartlead documents for this endpoint. The default, {"limit": 100}, returns the first 100 matching contacts.
Lists the contacts already saved for a Smart Prospect search.
Enter the Filter ID. This is the ID of a saved or fetched Smart Prospect search; use the Saved Searches API or Fetched Searches API template to find it.
Results are paged automatically, 1,000 records per page.
Checks whether a domain is available in the Smart Senders marketplace. Returns one record with the domain, whether it is available, and up to 30 suggested domains. Read-only; it buys nothing.
Enter the Domain Name to check, without the TLD (for example, acmeoutreach). Values are placed in the URL as typed, so use letters, numbers and hyphens only.
Enter the Vendor ID of the Smart Senders vendor to search with. Use the Get Vendors template to find it; Smartlead requires it even though its docs mark it optional.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Smartlead data sources can also be manually configured to ingest data from any valid Smartlead API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or optional filters that the templates do not send, such as campaign, client, or status filters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Most Smartlead endpoint URLs take the form https://server.smartlead.ai/api/v1/...; Smart Delivery, Smart Prospect, Smart Senders, and SmartServers use the hosts smartdelivery.smartlead.ai, prospect-api.smartlead.ai, smart-senders.smartlead.ai, and smartservers.smartlead.ai. See the Smartlead API reference for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Smartlead data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Smartlead destination, and select the Send to Destination option from the menu. Select the Smartlead connector from the list of available destination connectors, then select the credential that will be used to connect to your Smartlead account, and click Next; or, create a new Smartlead credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Smartlead endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time, so shape each record to match the request body that Smartlead documents for the endpoint. ID settings, such as a campaign or lead ID, are fixed on the destination and apply to every record it sends. Templates are marked Sends email when they cause Smartlead to send email, Spends credits when they consume Smart Prospect credits, and Side effect when they delete data or make other changes that cannot be undone from Nexla.
Creates a campaign from each record, in DRAFTED status with default settings. A record can carry name and client_id. Add sequences, a schedule, settings, and email accounts with the templates below before starting it.
Creates a subsequence (a child campaign that leads enter when a condition is met). Each record must include parent_campaign_id, and can carry a name and conditionEvents.
Creates or updates a campaign's email sequence steps. Each record carries a sequences array; steps with an id are updated, and steps without one are created.
Sends email: on an active campaign, the new or changed steps are what its leads receive next.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Sends a test email of one sequence step. Each record must include leadId and sequenceNumber, and can set selectedEmailAccountId and customEmailAddress.
Sends email: sends a test email for each record.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Detaches email accounts from a campaign's sender rotation. Each record must include email_account_ids. Smartlead rejects removing the last email account from an active campaign.
Side effect: removes mailboxes from the campaign.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Sets how spintax variations are distributed across a campaign's leads. Each record must include campaignId and spintaxDistributionMode (1 for incremental, 2 for random).
Deletes a campaign with all of its sequences, lead mappings, statistics, and settings. To keep the data, use Update Campaign Status to stop or archive the campaign instead.
Side effect: permanently deletes the campaign.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
The record's content is not sent; each record repeats the same request, so send a single record.
Adds leads to a campaign. Each record carries a lead_list array of leads (each with an email and optional name, company, and custom_fields), up to 400 leads per request, and optional settings that control duplicate, block-list, and unsubscribe checks.
Sends email: leads added to an active campaign start receiving its emails.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Sends a reply in a lead's email thread, from the campaign. Each record must include email_stats_id (the message being replied to) and email_body, and can set recipients, CC, BCC, a scheduled time, and attachments.
Sends email: sends the reply to the lead.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Connects an SMTP/IMAP email account. Each record carries the sender name and address and the SMTP and IMAP host, port, user name, and password, and sets warmup_enabled. Smartlead validates the connection before saving.
Connects a Gmail or Outlook email account with OAuth tokens that you already hold. Each record carries the sender name and address and the OAuth token details.
Links an untracked reply to a campaign lead, so it shows as that lead's reply. Each record must include emailCampaignId, leadMapId, and untrackedReplyId.
Creates a webhook that notifies a URL of events such as emails sent, opened, clicked, and replied. Each record must include webhook_url and association_type (user, client, or campaign).
Deletes a webhook by its ID, which each record carries in id. The Delete Campaign Webhook template below deletes a webhook by campaign and webhook ID instead.
Creates a webhook on a campaign, or updates one when the record includes the webhook's id. Each record must include name, webhook_url, and event_types.
Enter the Campaign ID. Use the Get All Campaigns template to find it.
Creates an API key for a client. Each record must include clientId and keyName. Use Reset Client API Key and Delete Client API Key to manage existing keys.
The new API key grants access to the client's data in Smartlead; store it securely.
Sends a one-off email outside of campaigns. Each record must include to, subject, and body, and can set the sender, reply-to address, and Base64-encoded attachments.
Sends email: sends an email immediately for each record.
Finds email addresses for up to 10 contacts per record. Each record carries a contacts array, each contact with firstName, lastName, and companyDomain.
Spends credits: spends Smart Prospect credits to find emails.
Reviews the contacts of a Smart Prospect search, syncing their metrics and status.
Enter the Filter ID. This is the ID of a saved or fetched Smart Prospect search; use the Saved Searches API or Fetched Searches API template to find it.
Smartlead destinations can also be manually configured to send data to any valid Smartlead API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Smartlead API expects JSON request bodies. Nexla adds the api_key query parameter from the credential, so leave it out of the endpoint URL.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Smartlead endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Smartlead endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.