Incoming SMS
Receive supported text events from Android, iPhone, Twilio or virtual-number channels.
Connect SMS and WhatsApp to Make.com Automation
Send supported incoming SMS and WhatsApp messages to a Make.com webhook, then classify enquiries, notify teams, update CRMs, create tickets, call business APIs or route approved replies through connected messaging channels.
SMS WebhooksWhatsApp AutomationAI AgentsReply API
Receive structured events
Send supported message data to a Make.com webhook.
Build visual scenarios
Branch, transform and connect business systems.
Control outbound actions
Authenticate replies and prevent duplicate sends.
One automation layer
Use Make.com for Both SMS and WhatsApp Scenarios
Normalize communication from several supported sources, then use Make.com to apply your own business logic and connect the systems that should act next.
Incoming WhatsApp
Forward supported QR or Meta Cloud message events into a Make.com webhook.
Scenario Routing
Branch by sender, keyword, source, schedule, intent or data returned by another service.
Controlled Replies
Use supported reply endpoints or SMS sending channels with explicit authentication.
Inbound webhookExplore Webhooks & APIs
Start a Make.com Scenario Whenever a Supported Message Arrives
Create a production webhook in Make.com and add its HTTPS URL as the appropriate AutoForward Text destination. A successful inbound event can then trigger the modules and connections authorized in that scenario.
✓ Capture available sender, message, source and timing data.
✓ Normalize phone numbers and classify the message.
✓ Route leads, support requests, alerts or appointment enquiries.
✓ Acknowledge the webhook quickly and handle longer work downstream.
WhatsApp reply API
Let Make.com Reply Through a Message-Specific Endpoint
For supported WhatsApp automation, the incoming payload can include a reply endpoint tied to that conversation. Send an authenticated POST request to that URL rather than storing provider credentials throughout the scenario.
Important: use the reply endpoint supplied by the event, an API key with the required permission, and a unique idempotency key for each logical reply.
Authorization: Bearer API key
Idempotency-Key: unique for one intended response
JSON body: reply text in the supported request format
Setup
Connect AutoForward Text to Make.com in Five Steps
Use Run once to capture a sample payload, map the fields, then activate the scenario and test the live webhook before relying on it.
1
Connect Sources
Add the Android, iPhone, WhatsApp, Twilio or virtual channels you need.
2
Create Webhook
Add a Make.com Custom Webhook module and copy its generated webhook URL.
3
Add Destination
Paste the webhook URL into the relevant AutoForward Text forwarding settings.
4
Build Logic
Validate fields, branch safely and connect only authorized service credentials.
5
Activate and Test
Activate the scenario and send fresh real messages from external sources.
Automation ideas
Turn Messages Into Useful Business Actions
Use deterministic routing for simple work and add AI only where it contributes meaningful classification, extraction or drafting.
Lead capture
Create or update HubSpot, GoHighLevel or Pipedrive records from supported enquiries.
Support triage
Classify topic and urgency, then create a ticket or notify the correct support queue.
Appointment scenarios
Extract requested dates and prepare a booking action for verification.
Order operations
Match order references and alert fulfillment or delivery teams.
Slack notifications
Post focused message alerts into sales, support or operations channels.
Database logging
Write approved message fields into a database, sheet or internal reporting system.
Sentiment and intent
Use an AI model to categorize communication while retaining human oversight.
Drafted replies
Generate a proposed answer, validate it, then send through a supported controlled reply path.
SMS versus WhatsApp replies
Receiving a Webhook Does Not Automatically Authorize Sending
Treat inbound processing and outbound messaging as separate capabilities. Each reply path needs its own supported source, authorization, recipient context and platform compliance.
WhatsApp replies
Use the supported event reply endpoint and account for Meta conversation-window or template requirements.
SMS replies
Require an outbound-capable Android gateway, Twilio, virtual number or another supported sending configuration.
Avoid loops
Mark automated output and ensure sent replies cannot re-trigger the same scenario indefinitely.
Use human approval
Require review for refunds, medical, legal, financial, safety or other high-impact responses.
Production safety
Secure Credentials, Validate Inputs and Design for Retries
Protect secrets
Keep API keys, webhook URLs and third-party credentials out of public scenario exports and screenshots.
Validate every event
Treat webhook payload fields as untrusted input before using them in queries, prompts or outbound calls.
Use idempotency
Generate one stable key per logical outbound reply so retries do not duplicate customer messages.
Limit AI authority
Restrict tools, destinations, spend and data access; log decisions and add human review where needed.
Troubleshooting
If a Make.com Scenario Does Not Receive or Reply
Test the source, inbound webhook and outbound action independently before debugging the entire scenario.
No execution appears
Confirm the scenario is active and AutoForward Text uses the current custom webhook URL.
Event fails before Make.com
Verify the source channel is connected and the message appears in AutoForward Text logs.
Reply is unauthorized
Check the Bearer API key, required permission and exact event reply endpoint.
Duplicate replies occur
Use a unique idempotency key per intended reply and keep it stable across retries.
Make.com FAQ
SMS, WhatsApp and Make.com Questions
Channel capabilities and outbound requirements depend on the connected provider and configuration.
Can AutoForward Text send incoming SMS to Make.com?+
Yes. Supported SMS from connected Android phones, iPhone workflows, Twilio numbers and virtual numbers can be sent to a Make.com webhook for routing and automation.
Can AutoForward Text send WhatsApp messages to Make.com?+
Yes. Supported incoming messages from connected WhatsApp accounts can be forwarded as webhook payloads to a Make.com scenario.
Can a Make.com scenario reply to an incoming WhatsApp message?+
For supported WhatsApp workflows, an incoming payload can include a message-specific reply endpoint. Make.com can send an authenticated POST request to that endpoint using an AutoForward Text API key and a unique idempotency key.
Why is an idempotency key required for replies?+
Automation platforms may retry failed or delayed requests. A unique idempotency key identifies one logical reply and helps prevent the same customer message from being sent more than once.
Can Make.com send an SMS reply?+
SMS sending or replies require a supported outbound SMS channel and the necessary permissions or provider configuration. Receiving an inbound webhook alone does not automatically authorize outbound SMS.
Can I connect an AI agent in Make.com?+
Yes. Make.com can pass supported message content to an AI model or agent, but businesses should validate outputs, protect personal data, restrict tool access and require human review for sensitive or high-impact actions.
What should my Make.com scenario return to AutoForward Text?+
For basic inbound delivery, acknowledge the webhook quickly with a successful response and perform slower work afterward where possible. Reply calls are separate authenticated requests to the supported reply endpoint.
How do I secure an AutoForward Text and Make.com scenario?+
Use HTTPS, protect webhook and API credentials, grant the minimum scopes, validate input, keep secrets outside scenario modules where possible, restrict execution access and avoid logging unnecessary message content.
Connect messages with Make.com
Turn SMS and WhatsApp Conversations Into Automated Scenarios.
Receive supported messages through webhooks, add business logic and build carefully controlled team, CRM and AI-agent actions.