HumationHuman + Automation
Back to Catalog

Lead collection with SendPulse and GPT-generated welcome emails/SMS

SendPulseSendPulse
30 views
2/3/2026
Basic ExampleData FetchingWebhookHTTP RequestAPI Integration
Official Page

How it works

This n8n template automates lead processing from your website. It receives customer data via a Webhook, stores the customer's contact (email or phone number) in the respective SendPulse address books, and uses the SendPulse MCP Server to send personalized welcome messages (email or SMS) generated using AI.

The template also includes built-in SendPulse token management logic with caching in the Data Table, which reduces the number of unnecessary API requests.

SendPulse’s MCP server is a tool that helps you manage your account through a chat with an AI assistant. It uses SendPulse API methods to get information and perform actions, such as request statistics, run message campaigns, or update user data.

MCP server acts as middleware between your AI assistant and your SendPulse account. It processes requests through the SendPulse API and sends results back to chat, so you can manage everything without leaving the conversation.

Once connected, the MCP server operates as follows:

  1. You ask your AI assistant something in chat.
  2. It forwards your request to the MCP server.
  3. The MCP server calls the API to get data or perform an action.
  4. The AI assistant sends the result back to your chat.

Set up

Requirements:

  • An active SendPulse account.
  • Client ID and Client Secret from your SendPulse account.
  • An API key from your OpenAI account to power the AI agent.

Set up steps:

  1. Get your OpenAI API Key - https://platform.openai.com/api-keys
  2. Add your OpenAI API Key to OpenAI Chat Model node in n8n workflow.
  3. Get your Client ID and Client Secret from your SendPulse account - https://login.sendpulse.com/settings/#api
  4. Add your Client ID and Client Secret to Workflow Configuration node.
  5. Add your Client ID and Client Secret to SendPulse MCP Client node as headers X-SP-ID Ρ– X-SP-SECRET in Multiple Headers Auth.
  6. In the Workflow Configuration node, change the names of the mailing lists, senderName, senderEmail, smsSender, routeCountryCode and routeType fileds as needed.
  7. Create a tokens table with the columns: hash (string), accessToken (string), tokenExpiry (string) in the Data tables section of your n8n platform account.

Lead Collection with SendPulse and GPT-Generated Welcome Emails/SMS

This n8n workflow automates the process of collecting leads via a webhook, generating personalized welcome messages using an AI agent, and then sending these messages through SendPulse. It intelligently decides whether to send an email or an SMS based on the lead's provided contact information.

What it does

This workflow streamlines your lead nurturing by performing the following steps:

  1. Listens for new leads: It starts by receiving lead data (e.g., name, email, phone number, preferred contact method) via an incoming webhook.
  2. Prepares lead data: It processes the incoming data, extracting and setting relevant fields like name, email, phone, and contactPreference.
  3. Generates personalized welcome message: An AI Agent (powered by an OpenAI Chat Model) creates a tailored welcome message based on the lead's name and preferred contact method.
  4. Determines contact method: It uses an 'If' node to check the contactPreference field.
    • If the preference is 'email', it proceeds to send an email.
    • If the preference is 'sms', it proceeds to send an SMS.
  5. Sends welcome email (if preferred): If the contact preference is email, it uses an HTTP Request node to send the GPT-generated welcome message as an email via SendPulse.
  6. Sends welcome SMS (if preferred): If the contact preference is SMS, it uses an HTTP Request node to send the GPT-generated welcome message as an SMS via SendPulse.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Webhook Source: An application or form configured to send lead data to the n8n webhook URL.
  • OpenAI API Key: An API key for OpenAI to power the AI Agent for message generation.
  • SendPulse Account: An active SendPulse account with API access for sending emails and SMS.
  • SendPulse API Credentials: Your SendPulse User ID and Secret to authenticate HTTP requests.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure the Webhook:
    • The "Webhook" node is the starting point. Copy its URL and configure your lead collection forms or applications to send lead data (e.g., name, email, phone, contactPreference) to this URL using a POST request.
  3. Configure OpenAI Credentials:
    • Locate the "AI Agent" node and ensure your OpenAI API key is configured as a credential for the "OpenAI Chat Model" node within it.
  4. Configure SendPulse Credentials:
    • For the "HTTP Request" nodes (one for email, one for SMS), you will need to configure them to use your SendPulse API. This typically involves:
      • Setting the URL to the appropriate SendPulse API endpoint for sending emails or SMS.
      • Setting the HTTP Method to POST.
      • Adding Headers for authentication (e.g., Authorization: Bearer YOUR_ACCESS_TOKEN). You might need an initial HTTP request to obtain an access token from SendPulse using your User ID and Secret, or use a custom authentication method.
      • Setting the Body to include the recipient's email/phone, sender details, and the generated message from the "AI Agent" node.
  5. Activate the workflow: Once all credentials and configurations are set, activate the workflow in n8n.

Now, whenever a new lead is submitted to your webhook, the workflow will automatically generate a personalized welcome message and send it via SendPulse based on their preferred contact method.

Related Templates

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

Wessel BulteBy Wessel Bulte
247

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting β€” all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow β€” reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n β€” combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

πŸŽ“ How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits βœ… Full Automation: Eliminates manual reading and data entry from incoming emails. βœ… Multi-Source Integration: Handles data from different email providers seamlessly. βœ… AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. βœ… Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. βœ… Time Efficiency: Processes emails in real time, improving productivity and response speed. *βœ… Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616