Set up a webhook destination
Discohook is built around sending long messages through webhooks. Its onboarding introduces support for Discord, Telegram, Slack, and other destinations, while the add-webhook form starts with a platform selector so each connection can be identified by service.
Create a named entry for the webhook you plan to use, then return to it when you need to send a message. This arrangement is helpful for keeping separate destinations for a community, team, announcement channel, or project.
Keep connection details organised
The setup form provides distinct fields for a webhook name, webhook URL, and default sender name. A built-in help prompt for obtaining a webhook URL keeps the required connection detail close to the form rather than hidden elsewhere in the app.
Use a recognisable label and sender name before adding a connection. Because a webhook URL can grant posting access, treat it like a private credential and only enter URLs for channels you are authorised to manage.
Send messages across supported platforms
Once a destination is added, Discohook is intended to send messages through the selected webhook service. The welcome flow specifically presents it as a way to move longer messages beyond a single platform while keeping the sending setup in a mobile interface.
It is a lightweight option for people who already have webhook endpoints and want a focused sender on Android. Message delivery depends on a valid endpoint, the chosen platform, and the permissions attached to that webhook.