Notifications via Slack, Discord, Telegram, WhatsApp

Get instant notifications in your team’s messaging platforms every time someone submits a form. This is faster than email for teams that already live in these tools, and it puts form submissions right where your team is already working and communicating. Instead of switching to email or logging into WordPress, your team sees new submissions in the same app they use all day.

Each messaging integration sends a formatted message containing the form name and all submitted field values. You can route different forms to different channels — for example, sales inquiries to #leads, support requests to #support, and job applications to #hiring.

Slack notifications use Slack Block Kit sections with two-column field blocks, so long submissions stay readable in busy channels. Empty optional fields and internal/system fields are skipped instead of being shown as placeholder dashes. Stripe submissions include readable Payment status, Payment amount, and Payment date rows. Telegram and WhatsApp notifications are routed through the Forge API notification services; the site must have a valid Form Forge license connection so requests can be authenticated without asking you for bot tokens or API keys.

Slack Setup

1. In your Slack workspace, go to the Apps directory (or visit api.slack.com/apps).
2. Create a new app (or select an existing one) and choose your workspace.
3. Under the app’s settings, go to Incoming Webhooks and toggle them on.
4. Click Add New Webhook to Workspace.
5. Select the channel where you want form submissions to appear (for example, #form-submissions or #leads).
6. Click Allow. Slack generates a Webhook URL (it looks like https://hooks.slack.com/services/T00000/B00000/XXXX).
7. Copy the Webhook URL.
8. In WordPress, go to Form Forge > Settings > Slack and paste the URL as the default webhook (applies to all forms).
9. Alternatively, paste the URL in an individual form’s Integrations settings to send only that specific form’s submissions to Slack.
10. Save settings.

Discord Setup

1. In your Discord server, right-click the channel where you want notifications (for example, #form-alerts).
2. Click Edit Channel.
3. Go to Integrations > Webhooks.
4. Click New Webhook, give it a name (for example, “Form Forge”), and click Copy Webhook URL.
5. In WordPress, go to Form Forge > Settings > Discord and paste the URL.
6. Or paste it in a specific form’s Integrations settings.
7. Save settings.

Telegram Setup — Personal chat

1. Open Telegram on your phone or desktop.
2. Search for @ForgeAPINotifyBot and start a conversation.
3. Send the message /start.
4. The bot replies with your Chat ID (a number like 123456789).
5. In WordPress, go to Form Forge > Settings > Telegram.
6. Paste your Chat ID and save.
7. All forms with notifications enabled will now send messages to your Telegram.

Telegram Setup — Group chat (team inbox)

To route submissions to a shared team group instead of one person’s DM:

1. Create or open a Telegram group with your teammates.
2. Add @ForgeAPINotifyBot to the group (Group settings → Add member → search ForgeAPINotifyBot).
3. The bot replies automatically with the group’s Chat ID — a negative number like -1002345678901.
4. Copy the Chat ID including the leading minus sign (it’s part of the ID, not a separator).
5. Paste it in Form Forge > Settings > Telegram > Chat ID and save.
6. Every member of the group now receives form submissions.

> Nothing happened after adding the bot? Telegram’s privacy mode hides plain /start in groups. Send /start@ForgeAPINotifyBot (the @-suffixed form) in the group and the bot will post the Chat ID. Or simply remove and re-add the bot — it auto-greets on join.

> Per-form routing: The global Form Forge > Settings > Telegram Chat ID is the default destination. In the form editor, the Telegram card only decides whether this form sends notifications and whether it overrides the global Chat ID. Leave the per-form Chat ID empty to use the global destination. Telegram messages escape MarkdownV2 reserved characters automatically, so form titles, IDs, timestamps, and field values containing symbols such as -, !, or # do not break delivery.

WhatsApp Setup

1. In WordPress, go to Form Forge > Settings > WhatsApp.
2. Turn on Enable WhatsApp integration globally.
3. Enter the recipient phone in international format, for example +998901234567.
4. Click Save Settings.
5. Open the form, enable WhatsApp notifications for that form, and save the form.

WhatsApp delivery uses the approved form_submission template. The recipient receives a short notification with the form name, submission status, submitter name, submitter email or phone when available, and a link back to the submission in WordPress admin.

If delivery fails, check that Form Forge is connected to Avakode and that the saved number includes the country code. No separate bot command or external setup is required for normal WhatsApp notifications.

Choosing the Right Platform

> Tip: You can use multiple messaging integrations simultaneously. Send lead form submissions to Slack for the sales team and to Telegram or WhatsApp for the founder’s personal alerts. There is no conflict between them.

> Good to know: Messaging notifications supplement email notifications — they do not replace them. Keep email notifications enabled as a reliable fallback, and use messaging notifications for speed and convenience.

Common Mistakes to Avoid

• Sending all forms to the same channel. Separate channels for different form types (leads, support, applications) keeps things organized.
• Forgetting to invite the bot to the channel (Telegram groups) or granting workspace access (Slack). Without proper permissions, messages fail silently.
• Not testing after setup. Send one test submission and verify it appears in the correct channel with all the expected data.

[Screenshot: A Slack channel showing a formatted form submission notification with the form name as the header and each field label and value listed below]

—