Start with one source channel and one destination. Add filters, translation, and more destinations after the first message arrives.
Before you start
Prepare an account that can read the source and a destination where you can configure a bot or webhook. Your account's current plan and available nodes determine instance and channel limits; check the console before expanding your setup.
| Item | Purpose | Example |
|---|---|---|
| Instance | Groups sources and forwarding rules | Team notifications |
| Source account | Connects to the platform that receives messages | Telegram personal account |
| Source channel | Selects the conversation to monitor | Project announcements |
| Destination | Receives the selected messages | Discord webhook |
| Channel rule | Connects a source channel to destinations and filters | Announcements to the team |
1. Create an instance
Open Forwarding instances, enter an instance name, and create the instance. Select an available execution node if the console asks. Open the newly created instance and confirm it is selected.
Paid users running their own server can first read the private node guide. If no platform node is available, use My feedback; ordinary users do not need to configure database credentials.
2. Connect a source account
In Source accounts, add the platform you want to receive messages from:
- Discord source and destinations: connect your own authorized source account; the source token is different from a destination bot token or webhook.
- Telegram source and bot destination: complete phone verification and two-step verification when required.
Connecting an account does not create a forwarding rule or expand its access to private channels. Select only conversations you are authorized to read and share.
3. Configure a channel rule
- Open Channel configuration and create a rule.
- Name the rule and select the connected source account.
- Select the source channel. Discord can load its channel list; Telegram can refresh its conversation list. Telegram manual entries require a numeric Chat ID with its minus sign preserved.
- Choose a destination type and enter that destination's credentials. Use the Discord or Telegram guides above for webhook and bot setup.
- For the first test, leave keyword and sender filters empty and translation or media processing disabled.
- Save the rule and confirm it is enabled.
One rule can contain several destinations of the same type. Create separate rules to send to different platform types. Full Chinese setup guides are available for Feishu, DingTalk, and notification destinations; these linked guides are in Chinese.
4. Start and verify a new message
- In Source accounts, start the required source if it is stopped. Stopping or restarting a source affects every plan using it.
- Check the source status, latest heartbeat time, and rule readiness. Runtime logs show health changes and errors; routine heartbeats and ordinary incoming-message events are hidden by default.
- After listening is ready, send a new message with a unique test identifier, such as
CF-EN-001. If you cannot post to the channel, wait for a new authorized source message. - Find the corresponding entry in Delivery records and check each destination result.
- Open the real destination and match the identifier, content, and channel position.
A saved rule, signed-in account, or online node does not prove receipt. Telegram may exclude your own messages or bot messages according to its independent source settings; use another authorized member's new message for a simple test.
Next steps
If the destination did not receive the message, follow forwarding troubleshooting. Once the basic route works, change one filter or content-processing setting at a time and test again. Telegram personal-account sources do not scan history; Discord history recovery is an optional, bounded feature rather than the default first-connection behavior.