Send SMS campaigns from Google Sheets and track delivery with SMS Vert Pro MCP
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 16 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Sheets and MCP Client.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Campaign settings (Edit Fields (Set)): sets 4 fields: sheet_url, sender, message_template…
- Read contacts (Google Sheets): uses Google Sheets
- Only contacts not yet sent (Filter): keeps only the items that match a condition
- Get STOP list (MCP Client): uses MCP Client
- Prepare messages (Code): runs custom JavaScript code
- Opted out? (If): checks a condition and branches into true / false
- Mark as opted out (Google Sheets): update
- Check message (MCP Client): uses MCP Client
- Characters OK? (If): checks a condition and branches into true / false
- Send SMS (MCP Client): uses MCP Client
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Filter
n8n-nodes-base.filter - MCP Client
@n8n/n8n-nodes-langchain.mcpClient - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait
From the author
Quick Overview This workflow manually sends an SMS via the SMS Vert Pro MCP server, waits 30 seconds, and then retrieves a delivery report for the SMS campaign using the returned campaign ID. How it works 1. Runs when you start the workflow manually. 2. Sends…