Send iPhone texts to Zapier, Make, n8n or Google Sheets

How it works

Your iPhone runs a Shortcuts Message automation when a matching text arrives. Fwrd’s action sends the text from the iPhone to your webhook URL as a POST with a JSON body holding one field, content, the message exactly as it arrived. Your automation tool picks it up from there.

Nothing passes through a Fwrd server, so the only places the text goes are your iPhone and the tool you point it at.

Connect your automation tool

1. 1Create a webhook triggerIn Zapier, start a Zap with Webhooks by Zapier and choose Catch Hook. In Make, add a Webhooks module and choose Custom webhook. In n8n, add a Webhook node set to POST and use its production URL. Copy the URL each one gives you.
2. 2Add Webhook in FwrdOn the iPhone, open Fwrd, tap +, choose Webhook, paste the URL, and tap Send Test Message. Your tool should show a request with a content field.
3. 3Create a Message automationOn iOS 27, open Shortcuts, tap Library, then Automation, then +. If you see Describe a shortcut, tap Edit. Tap Automation, then Message. On iOS 26, open the Automation tab, tap +, and choose Message.
4. 4Choose which texts to sendType a word the texts you want contain, such as code or order. To send nearly everything, type a single space.
5. 5Let it run on its ownMake it run without asking. On iOS 27, tap the arrow on the trigger and check Confirm Before Run is off. On iOS 26, choose Run Immediately and turn off Notify When Run.
6. 6Add Fwrd’s actionSearch for Forward and add Fwrd’s Forward Message to All Destinations. Tap its Message field and choose Shortcut Input (on iOS 26, Shortcut Input, then Message).
7. 7Finish your automationMap the content field to what you want: a new row in Google Sheets, a message to an AI agent, a ticket, or an email. Then send a real text to the iPhone to test the whole chain.

What your webhook receives

• A POST with Content-Type: application/json and a body of exactly {"content": "<the message text>"}.
• No sender’s number, timestamp or title. Most code and order texts name the service in the text itself.
• The same Idempotency-Key header on every retry of one message, so you can drop repeats.
• Any 2xx response counts as delivered. Redirects are refused and requests time out after 15 seconds.
• No authentication header. If your endpoint needs a secret, put it in the URL; Fwrd keeps the whole URL in the iPhone’s Keychain.

Full webhook guide

Tips for each tool

We haven’t tested Zapier, Make or n8n ourselves. Any HTTPS endpoint that accepts a JSON POST and answers with a 2xx status should work, so send a harmless test and check the content field arrives before you rely on it.

• Zapier: check your plan includes Webhooks by Zapier. Send Fwrd’s test message first so Zapier learns the content field.
• Make: run the scenario once, or click Re-determine data structure, then send Fwrd’s test message so Make sees the field.
• n8n: the test URL only listens while you’re testing in the editor. Paste the production URL into Fwrd and activate the workflow.
• Google Sheets: add the row from your Zap, scenario or workflow. Fwrd talks to the webhook, not to Sheets directly.

Questions about automation tools