Credentials for Telegram, Slack & Discord

The Low Stock Notification plugin’s webhook action can send stock alerts straight to Telegram, Slack, or Discord. Each platform needs a few credentials set up once. This guide shows you step by step where to find them.

Tip

You enter these values in the Flow Builder’s Send Webhook action — pick the platform there first, and the matching fields appear.

Telegram

Telegram needs two values: a bot token and a chat ID.

Create the bot token

1. Open Telegram and search for the contact @BotFather (the official bot with a blue verification checkmark).

2. Start the chat and send the command /newbot.

3. Choose a name (free choice), then a username that must end in bot (e.g. my_shop_stock_bot).

4. BotFather replies with the bot token. It looks like this:

   123456789:AAExampleTokenStringHere-abcdef1234567

   Copy this token into the Bot token field.

Caution

The bot token is like a password. Don’t share or publish it. If it leaks, send /revoke to BotFather and create a new one.

Find the chat ID

The chat ID decides where the message is sent — to you personally or to a group.

1. Important: first send your new bot any message (e.g. “Hello”). For a group, add the bot to the group and send a message there. Without this first message the bot doesn’t know the chat yet.

2. Open the following address in a browser, replacing <BOT-TOKEN> with your token:

   https://api.telegram.org/bot<BOT-TOKEN>/getUpdates

3. In the response, look for "chat":{"id":...}. The number after "id" is your chat ID (for groups it often starts with a minus sign, e.g. -1001234567890).

4. Copy this number into the Chat ID field.

Slack

Slack needs an incoming webhook URL. It is tied to a single channel.

1. Open api.slack.com/apps and click Create New App → From scratch.

2. Give it a name (e.g. “Stock Alerts”) and pick the target workspace. Confirm with Create App.

3. In the left menu open Incoming Webhooks and switch Activate Incoming Webhooks to On.

4. Click Add New Webhook to Workspace at the bottom.

5. Select the channel where the alerts should appear and confirm with Allow.

6. Slack now shows the webhook URL. It starts with:

   https://hooks.slack.com/services/...

   Copy it into the Slack webhook URL field.

Caution

Keep the webhook URL private — anyone who has it can post to your channel. The plugin only accepts URLs on hooks.slack.com.

Discord

Discord needs a webhook URL. It is created directly in Discord per channel — no bot and no developer account required.

1. Open your Discord server and click Server Settings (the gear next to the server name). You need the Manage Webhooks permission.

2. Go to the Integrations tab and click Webhooks → New Webhook.

3. Optionally give it a name and pick the channel where the alerts should appear from the dropdown.

4. Click Copy Webhook URL. The URL starts with:

   https://discord.com/api/webhooks/...

   Copy it into the Discord webhook URL field.

Caution

Keep the webhook URL private — anyone who has it can post to your channel. The plugin only accepts URLs on discord.com or discordapp.com.

Test the connection

Once you’ve entered the credentials, click Send test message in the action. The plugin sends a sample alert using your real settings — so you can see straight away whether the connection works before the flow goes live. If the test fails, an error message appears — depending on the cause: required fields are missing, the bot token format is invalid, or the URL is not allowed. For all other failures (e.g. a wrong token, wrong chat ID, or the service being unreachable) the message reads: “The test message could not be delivered. Please check your credentials and try again.” Technical details such as URLs or error codes are never shown.

Custom message template (Pro)

With the Pro version you can write the message text yourself per platform and insert product placeholders with a click ({{ product.name }}, {{ product.number }}, {{ product.stock }}, {{ salesChannel }}, {{ timestamp }}). Without Pro a default message is sent — the credentials above work in both cases.