Twilio SMS: Send, Log, and Notify via Airtable and Slack

This workflow automates sending SMS via Twilio, logging results to Airtable, and notifying via Slack. Key nodes include Webhook Trigger (starts via POST), Validate Input (checks phone/message), Process SMS Request (sanitizes data), Send SMS via Twilio (Twilio API call), Log SMS to Database (stores in Airtable), Send Notification (posts to Slack), Success Response (returns results), and error nodes (Validation/Processing/SMS Error Response) for failures.\n\nSetup Requirements and Configuration: Install n8n from n8n.io for self-hosting or sign up at cloud.n8n.io. Follow prompts or create a cloud account. Obtain Twilio credentials from twilio.com: sign up, log in, go to 'Console' > 'Account Info,' and copy Account SID and Auth Token. Get an Airtable Personal Access Token from airtable.com: log in, navigate to 'Account' > 'API Access,' and generate a token with data write permissions. In n8n, import the JSON workflow. Configure Send SMS via Twilio with Twilio credentials and Log SMS to Database with Airtable token under ‘Credentials.’ Set Slack webhook URL in the Send Notification node. Configure Webhook Trigger path to ‘send-sms’ for POST requests. Ensure server supports API calls.\n\nTesting and Deployment Steps: Test with Postman using a POST request to the Webhook URL. Example JSON: {'body': {'phone': '+1234567890', 'message': 'Test SMS'}}. Success responses return 200 with request_id, to_phone, twilio_response (sid/status), and logged_at. Error nodes return 400 for missing phone/message, 422 for invalid formats (e.g., short phone number), or 500 for API failures. Check logs for errors like ‘Invalid Twilio credentials’ or ‘Airtable write failed,’ and verify credentials or input formats. Activate workflow in n8n. Validate output: ensure request_id is unique, to_phone matches input, and twilio_response.sid exists. Debug errors using n8n logs for issues like rate limits, invalid Slack webhook, or Airtable access problems.