Servers and private channels
Set up Discord
Forward selected iPhone messages to a Discord channel with a channel webhook.
How this destination works
Fwrd makes a direct HTTPS attempt from the iPhone to this destination when it is active. The destination service still controls final acceptance and delivery.
Before you begin
- A Discord server where you have the Manage Webhooks permission — server owners already have it
- A channel reserved for the messages you intend to forward
- Fwrd installed on the iPhone that receives the messages
Set up the destination
8 steps
Open the server’s integrations
In Discord, open Server Settings and select Integrations. If the server already has webhooks, open the Webhooks card to see them.
Create the webhook
Choose New Webhook, or Create Webhook on a server that has none yet. Give it a name, then pick the channel it should post to from the channel dropdown.
Copy the webhook URL
Choose Copy Webhook URL. Anyone who has it can post to that channel, so treat it like a password and keep it out of shared documents.
https://discord.com/api/webhooks/000000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXAdd Discord in Fwrd
On the iPhone, open Destinations, tap Add Destination, and choose Discord. Give it a name you will recognise in the list.
Paste the URL into Fwrd
Paste the whole URL into the Configuration field. Fwrd checks the address before it lets you continue, so a shortened or hand-edited URL will not be accepted.
Configuration ← Discord channel webhook URLSend a test message from Fwrd
Tap Send Test Message and check that it arrives. This proves the credential and the network path. It does not prove the SMS automation, so do not stop here.
Save and keep the destination active
Tap Save Destination and leave Destination Active switched on. An inactive route stays saved on the iPhone but is skipped when messages arrive.
Destination Active ← OnProve it with a real message
Text yourself something that contains nothing private and watch it arrive at the destination. Try it with the iPhone unlocked first, then locked, because locked is the state it will usually be in.
What counts as verified
A saved destination, completed checklist, or successful connection test is setup evidence—not delivery proof. Final verification requires a sanitized incoming SMS on a physical iPhone and the matching result at Discord, including a locked-device test when that is part of your intended use.