Yes, Discord is supported as a signal source, next to Telegram, email and TradingView. PipSync reads Discord channels through one shared PipSync bot that you invite to your server. You do not need your own bot or a token.
Steps
- Channels → Add Discord → Connect with Discord. Discord asks to share your user name and your server list. PipSync cannot read your messages this way.
- PipSync lists the servers you own or manage. Click the signal server, then Invite the bot now. Discord asks for two read-only permissions, View Channels and Read Message History. Confirm on Discord.
- Back in PipSync click Bot invited — continue, tick one or more channels, optionally set a name and provider, and click Save channel(s).
- New channels start within about 30 seconds. Only new messages are read, never older ones.
You must own the server or have Manage Server
Discord only lets the server owner, or people with the Manage Server permission, add a bot. If you are only a member of the signal server, PipSync does not list it ("No server found where you have the Manage Server permission"). Ask the owner or an admin to connect the channel from their own PipSync account, or to give you Manage Server.
Good to know
- Each connected channel counts as one signal source against your plan's limit; the Free plan allows one source.
- Text and image signals are read, and so are bot and webhook posts including their embeds.
- A private channel needs View Channels and Read Message History for the PipSync role (Edit Channel → Permissions).
- Never give the bot Administrator rights; it asks for read access only and never posts.
- If a channel is saved but no signals arrive, check that the PipSync role still has those two permissions, then see A message arrived but no signal was created.
If the Connect with Discord button reports a setting on PipSync's side, message us in the support chat.