My workflow 5

A simple WhatsApp messaging workflow that receives webhook data and sends automated WhatsApp responses using Twilio's messaging service.

Purpose

No business context provided yet — add a context.md to enrich this documentation.

How It Works

This workflow operates as a basic webhook-to-WhatsApp bridge:

1. Webhook Reception: The workflow listens for incoming POST requests on a specific webhook endpoint
2. Message Processing: It extracts phone number and message content from the incoming webhook data
3. WhatsApp Response: Using Twilio's API, it sends a WhatsApp message back to the original sender

The workflow appears to be designed for automated WhatsApp responses, potentially for customer service, notifications, or chatbot interactions.

Workflow Diagram

graph TD
    A[Webhook Trigger] --> B[Send WhatsApp response E!BA2]

    A -.->|phoneNumber| B
    A -.->|WaId from body| B
    A -.->|output message| B

Trigger

Webhook (POST): The workflow starts when a POST request is made to the webhook endpoint 33898c22-f5f0-45f0-9983-3fd19c2daebb. This could be triggered by: - External applications sending webhook notifications - Other systems that need to send WhatsApp messages - API integrations requiring WhatsApp messaging capabilities

Nodes Used

Node Type	Node Name	Purpose
Webhook	Webhook	Receives incoming POST requests and extracts data
Twilio	Send WhatsApp response E!BA2	Sends WhatsApp messages via Twilio's API

External Services & Credentials Required

Twilio

• Purpose: WhatsApp message delivery
• Credentials needed: Twilio API credentials (Account SID, Auth Token)
• Credential name in workflow: "Waringa"
• Requirements:
  • Active Twilio account
  • WhatsApp Business API access through Twilio
  • Verified phone numbers for WhatsApp messaging

Environment Variables

No environment variables are explicitly configured in this workflow. All configuration appears to be handled through: - Webhook endpoint configuration - Twilio credential setup - Dynamic data extraction from incoming webhook payloads

Data Flow

Input (Webhook)

The webhook expects a POST request with: - phoneNumber: Source phone number for the WhatsApp message - body.WaId: WhatsApp ID of the recipient - output: The message content to be sent

Processing

• Extracts phone number from the webhook payload
• Uses the WaId from the request body as the recipient
• Takes the output field as the message content

Output

• Sends a WhatsApp message via Twilio
• Returns Twilio API response (delivery status, message ID, etc.)

Error Handling

No explicit error handling is configured in this workflow. Consider adding: - Error handling for failed Twilio API calls - Validation for required webhook fields - Retry logic for message delivery failures - Logging for debugging purposes

Known Limitations

• No input validation on webhook data
• Missing error handling for API failures
• No rate limiting or message queuing
• Workflow is currently inactive (not deployed)
• Limited to single message responses (no conversation flow)

Related Workflows

No related workflows identified from the current context.

Setup Instructions

1. Import Workflow

1. Copy the workflow JSON
2. In n8n, go to Workflows → Import from JSON
3. Paste the JSON and save

2. Configure Twilio Credentials

1. Go to Credentials in n8n
2. Create new Twilio API credential
3. Enter your Twilio Account SID and Auth Token
4. Name it "Waringa" or update the node to use your credential name
5. Ensure your Twilio account has WhatsApp Business API access

3. Test the Webhook

1. Activate the workflow
2. Note the webhook URL: https://your-n8n-instance.com/webhook/33898c22-f5f0-45f0-9983-3fd19c2daebb
3. Send a test POST request with the required fields:

   {
     "phoneNumber": "+1234567890",
     "body": {
       "WaId": "+0987654321"
     },
     "output": "Hello from n8n!"
   }
   

4. Production Considerations

• Add input validation
• Implement error handling
• Set up monitoring and logging
• Configure rate limiting if needed
• Test with your specific WhatsApp Business setup