Automate 30-day coach training with SMS, Twilio & Google Sheets

Ronnie Craig

57 views

2/3/2026

Slack Google Drive Automation Attachments Email

Official Page

Coach Onboarding & Training Automation - Setup Guide

Prerequisites

n8n instance (self-hosted or cloud)
Google Sheets account
Twilio account with SMS-enabled phone number

Setup Steps

1. Configure Settings Node

Update the "Configuration Settings" node with:

GOOGLE_SHEET_ID: Your Google Sheets ID from the URL
TWILIO_PHONE_NUMBER: Your Twilio number (format: +1XXXXXXXXXX)
BUSINESS_NAME: Your company name
TRAINING_PROGRAM_NAME: Your program name
MAIN_PRODUCT_NAME: Your main product/service

2. Create Google Sheets Database

Create a new Google Sheet with 2 tabs:

Sheet1 (Coaches) - Column headers:

Sheet2 (Training Content) - Column headers:

Day | Topic | Message | Audio_URL

Add your 30-day training content to Sheet2 (rows 1-30).

3. Setup Credentials in n8n

Google Sheets OAuth2 API:

Name: "Google Sheets account"
Follow Google OAuth setup in n8n

Twilio API:

Name: "Twilio account"
Account SID: Your Twilio SID
Auth Token: Your Twilio Auth Token

4. Configure Webhooks

Registration Webhook: /webhook/coach-registration

Accepts POST with: name, phone, email, goals

Response Webhook: /webhook/coach-response

Configure in Twilio for incoming SMS

5. Activate Workflow

Enable the workflow and test with sample data.

Testing

Test registration:

curl -X POST https://your-n8n-url/webhook/coach-registration \
  -H "Content-Type: application/json" \
  -d '{"name":"Test Coach","phone":"5551234567","email":"test@example.com","goals":"Test goals"}'

Troubleshooting
SMS not sending:

Verify Twilio credentials
Check phone number format (+1XXXXXXXXXX)
Confirm Twilio account has balance

Google Sheets errors:

Verify OAuth permissions
Check column names match exactly
Ensure Sheet ID is correct

Daily automation not running:

Check cron schedule is active
Verify timezone settings
Confirm coaches have "active" status

### 3. **description.md** - Marketplace Description
(Use the marketplace description from artifact #2, or create a shorter version):
```markdown
# Coach Onboarding & Training Automation

Automate coaching business onboarding with SMS-based 30-day training programs.

## Features
- Automated coach registration via webhook
- Daily training SMS delivery (9 AM)
- Smart keyword auto-responses
- Progress tracking in Google Sheets
- Weekly motivation messages
- Audio lesson support
- SMS compliance (STOP handling)

## Use Cases
- Business coaches scaling onboarding
- Sales trainers automating team development
- Course creators with SMS follow-up
- Network marketing team training

## Requirements
- Google Sheets account
- Twilio account with SMS number

4. OPTIONAL: Screenshots
If possible, include:

Workflow overview screenshot
Sample Google Sheets structure
Example SMS messages received

Automate 30-Day Coach Training with SMS (Twilio) & Google Sheets

This n8n workflow automates the process of sending daily SMS messages for a 30-day coach training program, managing participant data in Google Sheets. It allows for scheduled delivery of training content and handles new enrollments.

What it does

Triggers Daily: The workflow is scheduled to run once every day.
Fetches Participant Data: It reads all rows from a specified Google Sheet, which presumably contains participant information including their phone numbers, current day in the training, and the content for each day.
Processes Each Participant: For each row (participant) fetched from the Google Sheet:
- Calculates Next Day: It increments a "Day" counter for the participant.
- Filters Active Participants: It checks if the participant's "Day" counter is within the 30-day training period.
- Sends Daily SMS: If the participant is still active in the training, it constructs and sends an SMS message using Twilio, delivering the appropriate training content for their current day.
- Updates Google Sheet: After sending the SMS, it updates the Google Sheet with the participant's new "Day" counter.
Responds to Webhook (Placeholder): The workflow includes a "Respond to Webhook" node, suggesting it might also be designed to receive and acknowledge external triggers or data, though its current connections are empty.

Prerequisites/Requirements

n8n Instance: A running instance of n8n.
Google Sheets Account: A Google account with access to Google Sheets. You will need to configure Google Sheets credentials in n8n.
Twilio Account: A Twilio account with an active phone number capable of sending SMS messages. You will need to configure Twilio credentials in n8n.
Google Sheet: A Google Sheet set up with columns for participant data, including at least a "Day" counter and a "Phone Number" column, and likely columns for the 30 days of training content.

Setup/Usage

Import the Workflow: Import the provided JSON into your n8n instance.
Configure Credentials:
- Google Sheets: Configure your Google Sheets OAuth2 or API Key credentials. Ensure the service account or user has read/write access to your training Google Sheet.
- Twilio: Configure your Twilio Account SID and Auth Token credentials.
Customize Google Sheets Node (ID: 18):
- Specify the Spreadsheet ID of your training Google Sheet.
- Specify the Sheet Name (e.g., "Sheet1").
- Ensure the "Operation" is set to "Read" for fetching data and "Update" for writing back.
- Map the columns correctly for reading and writing participant data.
Customize Twilio Node (ID: 45):
- Set your Twilio Phone Number (the "From" number).
- Map the "To" phone number to the relevant column from your Google Sheet (e.g., {{ $json.phoneNumber }}).
- Construct the "Body" of the SMS message using data from your Google Sheet (e.g., {{ $json['Day' + $json.Day] }} to dynamically fetch content for the current day).
Configure Schedule Trigger (ID: 839):
- Set the desired Interval (e.g., "Every Day" at a specific time) for the workflow to run.
Activate the Workflow: Save and activate the workflow.

This workflow provides a robust foundation for automating a personalized, drip-feed training program via SMS, leveraging the power of Google Sheets for content and participant management.

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.

By Ranjan Dailata

161

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

By Daniel Nkencho

601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

By Le Nguyen

942