Best iPhone SMS to Webhook App, Compared

The best iPhone SMS to webhook app posts each text from your iPhone to your HTTPS endpoint as simple JSON, retries safely without creating duplicates, and lets each endpoint keep only the texts it needs. Fwrd does that with no account and no Fwrd server, sending a stable Idempotency-Key with every attempt, and its free plan includes webhooks for 15 forwards a month. It needs iOS 26 or later, so if your iPhone runs an older version, the table below shows which apps run on it.

What you need: an iPhone, an HTTPS endpoint that accepts a JSON POST and answers with a 2xx status, such as an n8n, Make or Zapier trigger, and a rule for which texts to forward.

Which iPhone apps send texts to a webhook?

These five US App Store apps list a webhook or API as a destination. Ratings, minimum iOS and what each says about its servers come from Apple’s App Store data and each app’s own description, checked on November 4, 2026.

Prices and plans change, so check the purchase screen in your own storefront. For every destination, see the best SMS forwarding apps for iPhone.

What matters when the destination is a webhook

• A payload you can rely on. A fixed, small body is easier to parse than one that changes with settings. Know which field holds the text before you build on it.
• Retries without duplicates. Networks drop answers, so a sender retries. An idempotency key that stays the same across attempts lets your endpoint drop the repeats.
• Where the URL lives. Many endpoints carry their secret in the URL, so it belongs in the iPhone’s Keychain.
• Headers. If your endpoint needs custom headers or an auth token in a header, check the app supports them. Re:Text lists custom headers and auth tokens; Fwrd sends none, so a secret goes in the URL.

Why I’d pick Fwrd for a webhook

I make Fwrd, so here’s my case, and each point is on its App Store page and webhook page:

• A small, fixed body: {"content": "<text>", "text": "<text>"}, which Mattermost and Rocket.Chat read as is, plus a sender field only if you turn on Include Who Sent It. A Google Chat webhook gets only text.
• The same Idempotency-Key on every attempt for one message, so your server can drop retries it has seen.
• Straight from your iPhone, with no account and no Fwrd server, and the URL in the Keychain.
• A filter on each endpoint, by words, verification codes or hours, and Activity on the iPhone shows every forward and its result.
• Built for agents and QA jobs. An AI agent or a QA job waiting for a one-time code gets it as JSON seconds after it arrives.

How to send iPhone texts to a webhook with Fwrd

1. Get an HTTPS endpoint that accepts a JSON POST, such as an n8n Webhook node’s production URL or a Make or Zapier catch hook.
2. Add Webhook in Fwrd. Tap +, choose Webhook, paste the URL and tap Send Test Message, so your tool sees the content field.
3. Create a Message automation in Shortcuts and set Message Contains to a word your texts include, such as code.
4. Let it run without asking. Turn off Confirm Before Run on iOS 27, or choose Run Immediately on iOS 26.
5. Add Fwrd’s action, Forward Message to All Destinations, with Message set to Shortcut Input.

The n8n post and the SMS API post go further.

What sending texts to a webhook can’t do

• No app can read your texts on its own. iPhone gives apps no access to your messages, so each one needs the Shortcuts automation you set up.
• It can’t forward texts you already have, only new ones that arrive after the automation is on.
• It can’t reach plain HTTP or local addresses. Fwrd accepts only HTTPS, so a local server needs a tunnel or host that gives it an HTTPS address.
• It doesn’t add auth headers or follow redirects, and a request times out after 15 seconds.