Tracking cold email engagement metrics using Smartlead and Google Sheets
Workflow: Track Email Campaign Engagement Analytics with Smartlead and Google Sheets
Automatically fetch lead-level email engagement analytics (opens, clicks, replies, unsubscribes, bounces) from Smartlead and update them in Google Sheets.
Use this to keep a single, always-fresh source of truth for campaign performance and sequence effectiveness.
Summary
Pull Smartlead campaign analytics on a schedule and write them to a Google Sheet (append or update).
Works with pagination, avoids duplicates via a stable key, and is ready for dashboards, pivots, or BI tools.
What This Workflow Does
- Collects campaign stats from Smartlead (per-lead, per-sequence).
- Handles pagination safely (offset/limit).
- Writes to Google Sheets using appendOrUpdate with a matching column to prevent duplicates.
- Can run on a schedule for near real-time analytics.
Node Structure Overview
| Step | Node | Purpose |
|---|---|---|
| 1️⃣ | Schedule Trigger | Starts the workflow on a cadence (e.g., hourly) |
| 2️⃣ | Code (Pagination Generator) | Emits {offset, limit} pairs (e.g., 0..9900, step 100) |
| 3️⃣ | Split in Batches | Sends each pagination pair to the API sequentially |
| 4️⃣ | HTTP Request (Smartlead) | GET /campaigns/{campaign_id}/statistics with offset/limit |
| 5️⃣ | Split Out | Turns the API data[] array into one item per lead record |
| 6️⃣ | Google Sheets (appendOrUpdate) | Upserts rows by stats_id into EngagedLeads tab |
| 7️⃣ | Loop Back | Continues until all batches have been processed |
Step-by-Step Setup
-
Prerequisites
- Smartlead account + API key with access to campaign statistics.
- Google account + Google Sheets OAuth connected in n8n.
-
Create the Google Sheet
- Spreadsheet name: Email Analytics (can be anything).
- Tab name: EngagedLeads.
- Add these exact headers (first row):
lead_name, lead_email, lead_category, sequence_number, stats_id, email_subject, sent_time, open_time, click_time, reply_time, open_count, click_count, is_unsubscribed, is_bounced
-
Configure the Schedule Trigger
- Choose a frequency (e.g., every 2 hours).
- If you’re testing, set a single run or a short cadence.
-
Configure the Code Node (Pagination)
- Emit N items like:
{ "offset": 0, "limit": 100 } { "offset": 100, "limit": 100 } ... - 100 is a good default
limit. For up to 10,000 records, generate 100 offsets.
- Emit N items like:
-
Configure the Smartlead API Node
- Method: GET
- URL:
https://server.smartlead.ai/api/v1/campaigns/{campaign_id}/statistics - Query parameters:
api_key=<YOUR_SMARTLEAD_API_KEY>offset={{ $json.offset }}limit={{ $json.limit }}
- Map response to JSON.
-
Split Out the Response
- Use a Split Out (or similar) to iterate over
data[]so each lead record is one item.
- Use a Split Out (or similar) to iterate over
-
Google Sheets Node (Append or Update)
- Operation: appendOrUpdate.
- Document: Your Email Analytics sheet.
- Sheet/Tab: EngagedLeads.
- Matching Column:
stats_id. - Map fields from Smartlead response to sheet columns:
lead_name← lead name (or composed from first/last if provided)lead_email← emaillead_category← category/type if availablesequence_number← sequence step numberstats_id← stable identifier (e.g., Smartleadstats_idor message id)email_subject← subjectsent_time,open_time,click_time,reply_time← timestampsopen_count,click_count← integersis_unsubscribed,is_bounced← booleans
- If the same
stats_idarrives again, the row is updated, not appended.
-
Test and Activate
- Run once manually to verify API and sheet mapping.
- Check the sheet for new/updated rows.
- Activate the workflow to run automatically.
Smartlead API Reference (Used by This Workflow)
- Endpoint GET https://server.smartlead.ai/api/v1/campaigns/{campaign_id}/statistics
- Required query parameters
api_key(string)offset(number)limit(number)- Typical response (trimmed example)
{
"data": [
{
"lead_name": "Jane Doe",
"lead_email": "jane@example.com",
"sequence_number": 2,
"stats_id": "15b6ff3a-...-b2b9f343c2e1",
"email_subject": "Quick intro",
"sent_time": "2025-10-08T10:18:55.496Z",
"open_time": "2025-10-08T10:20:10.000Z",
"click_time": null,
"reply_time": null,
"open_count": 1,
"click_count": 0,
"is_unsubscribed": false,
"is_bounced": false
}
],
"total": 1234
}
Google Sheets Structure (Recommended)
Spreadsheet: Email Analytics
Tab: EngagedLeads
Columns:lead_name, lead_email, lead_category,
sequence_number, stats_id,
email_subject, sent_time, open_time, click_time, reply_time,
open_count, click_count, is_unsubscribed, is_bounced
Matching Column: stats_id (prevents duplicates and allows updates)
Customization Tips
-
Multiple Campaigns
Duplicate the workflow and set a different{campaign_id}and/or write results to a separate tab in your Google Sheet. -
Batch Size
Increase or decrease thelimitvalue (e.g.,200) in your Code node if you want fewer or more API calls. -
Filtering
Add a Code or IF node to skip rows whereis_bounced = trueoris_unsubscribed = true. -
Dashboards
Create a new tab named Dashboard in Google Sheets and visualize your data using built-in charts or connect it to Looker Studio for advanced visualization. -
Enrichment
Join this dataset with your CRM data (e.g., HubSpot or Salesforce) usinglead_emailas a key to gain deeper customer insights.
Security and Publishing Notes
-
Do not hardcode your Smartlead API key in the workflow export.
Use n8n credentials or environment variables instead. -
When sharing the template publicly, replace sensitive values with placeholders like:
<YOUR_SMARTLEAD_API_KEY>and<YOUR_GOOGLE_SHEET_ID>. -
Keep your Google Sheet private unless you intentionally want to share it publicly.
Troubleshooting
-
No rows in Sheets
Verify that the API response includesdata[], confirm that the Split Out node is configured correctly, and check field mappings. -
Duplicates
Ensure the Google Sheets node has its matching column set tostats_id. -
Rate Limits
Increase the schedule interval, add a short Wait node between batches, or reduce thelimitsize. -
Mapping Errors
Ensure that column names in Sheets exactly match your field mappings — they are case-sensitive. -
Timezone Differences
Smartlead timestamps are in UTC. Convert them downstream if your local timezone is different.
Example Use Case
Run this workflow hourly to maintain a live, company-wide Email Engagement Sheet.
- Sales teams can monitor replies and active leads.
- Marketing teams can track open and click rates by sequence.
- Operations can export monthly summaries — no Smartlead login required.
Tags
Smartlead EmailMarketing Automation GoogleSheets Analytics CRM MarketingOps
n8n Workflow: Smartlead and Google Sheets Engagement Tracking
This n8n workflow is designed to track email engagement metrics from a Smartlead campaign and store them in a Google Sheet. It periodically fetches campaign data, processes it to extract relevant engagement information, and then appends this data to a specified Google Sheet.
What it does
This workflow automates the following steps:
- Schedules Execution: The workflow is triggered on a recurring schedule (e.g., daily, hourly) to check for new engagement data.
- Fetches Smartlead Campaigns: Makes an HTTP request to the Smartlead API to retrieve a list of campaigns.
- Processes Campaign Data: Uses a Code node to iterate through the fetched campaigns and extract specific engagement metrics (e.g., opens, clicks, replies, bounces). It likely transforms the raw API response into a structured format suitable for Google Sheets.
- Splits Data for Batch Processing: If multiple campaigns are processed or if a single campaign yields multiple data points, the "Loop Over Items" node prepares the data for individual processing.
- Appends to Google Sheet: For each processed data item (representing campaign engagement), it appends a new row to a designated Google Sheet, recording the extracted metrics.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Smartlead Account: Access to the Smartlead API and an API key.
- Google Account: A Google account with access to Google Sheets.
- Google Sheets Credential: An n8n credential configured for Google Sheets.
- HTTP Request Node (Smartlead API): The HTTP Request node will need to be configured with the Smartlead API endpoint and authentication (e.g., API key in headers).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up a Google Sheets credential in n8n if you haven't already.
- The
HTTP Requestnode will need to be configured with your Smartlead API key and the correct endpoint to fetch campaign data.
- Configure Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name where you want to store the engagement metrics.
- Ensure the column headers in your Google Sheet match the data being output by the
Codenode.
- Configure Schedule Trigger: Adjust the
Schedule Triggernode to your desired frequency for checking and updating engagement metrics (e.g., once every 24 hours). - Activate the Workflow: Once configured, activate the workflow to start tracking your Smartlead campaign engagement.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte