How to Send Messages to Discord with the New Integration Block
•
5 minutes read

The new Discord Integration block enables your Release0 agents to send real-time messages directly into Discord channels. This opens up a wide range of internal automation and notification workflows — from lead alerts and booking logs to AI feedback tracking.
This blog post will walk you through how the block works, how to configure it, and how to use it for practical business and support workflows.
🤖 What Is the Discord Block?
The Discord block is a type of Integration Block in Release0 that sends a message to a Discord server via a Webhook URL. Once configured, it allows your agent to notify a team, log a submission, or broadcast any information collected during the chat.
It supports variable interpolation — meaning you can insert user answers dynamically — and Markdown formatting to enhance message readability.
Example Usage
If a user fills out a contact form in your agent, you can send the data to your Discord sales channel like this:
_10New blog post_10_10Name: {{user_name}}_10Title: {{title}}_10Message: {{user_message}}_10Image URL: {{image_url}}
This will appear formatted as a readable message in the Discord channel linked to the webhook.
🛠️ Step-by-Step Setup
1. Create a Webhook in Discord
To post messages into a Discord channel, you need to create a webhook URL:
- Go to Discord > open your server settings
- Select the channel where you want to receive messages
- Click Integrations > Webhooks > New Webhook
- Name it, assign a target channel, and click Copy Webhook URL
2. Add the Discord Block to Your Agent
In your Release0 flow editor:
- Drag the Discord block into your workflow
- Paste the copied Webhook URL
- Compose your message using plain text or Markdown, and insert variables
3. Choosing message type
There are 3 available options to configure the Discord block:
- Send simple message: This allows you to send a basic text message to the Discord channel.
- Send status message: This option sends a message with the status of the agent with 4 status options:
Info
,Success
,Warning
, andError
. This is useful for sending updates about the agent's activities. - Send advanced message: This allows you to send a more complex message with additional formatting, such as thumbnails, author name, and more. This is useful for sending rich content messages to the Discord channel.
4. Test the Flow
Use the Preview mode to submit test data and confirm the message is received in your Discord channel. Adjust formatting if needed.
✅ Common Use Cases
🚀 1. Lead Alerts
Notify your sales or marketing team immediately when a new user submits their information.
Use this setup in a contact or lead-gen form. Include fields like name, email, selected service, and even UTM data:
_10📩 New lead!_10Name: {{name}}_10Email: {{email}}_10Plan: {{user_plan}}_10UTM Source: {{utm_source}}
Send to a #sales-leads channel with optional pings like @sales-team
.
📅 2. Booking Confirmations
Log every new event, call, or delivery booking made through your agent.
Pair this with blocks like Date, Address, and Phone to capture structured data.
Example message:
_10📅 New Booking Submitted_10Date: {{event_date}}_10Location: {{event_address}}_10Contact: {{user_phone}}
Send to a channel like #client-bookings or #field-ops.
🧠 3. AI Response Logs
Monitor what your AI blocks (e.g. OpenAI, Groq, Claude) are responding with, for moderation or QA.
Use this when running advanced flows with AI content generation. Send user queries and AI outputs to a mod-only Discord channel:
_10👁️ AI Interaction Logged_10User: {{user_message}}_10AI Response: {{ai_response}}_10Time: {{timestamp}}
This allows human oversight and review of sensitive conversations.
🔔 4. Conditional Alerts
Trigger Discord messages only when specific thresholds or logic are met.
Pair the Discord block with a Condition block to create alerting systems. Example:
- If
{{user_budget}} > 10000
, trigger a message to #vip-alerts
Message:
_10🚨 High-value lead detected!_10Budget: ${{user_budget}}_10Name: {{name}}
🔐 Webhook Security Best Practices
Webhook URLs give full message access to the target channel. Treat them like passwords.
- Do not expose webhook URLs in agent text messages or frontend links
- Create separate webhooks for test and production environments
- Revoke and regenerate webhooks if you suspect exposure
🧪 Debugging Tips
-
If nothing appears in Discord:
- Double check the webhook URL (no spaces or typos)
- Test the webhook manually with a tool like curl or Postman
- Make sure the block is placed after user input is collected
-
If variables like
{{email}}
are blank:- Ensure they’re captured earlier in the flow
- Check spelling — variables are case sensitive
📊 Analytics and Tracking
While Discord doesn’t offer click tracking, you can use Release0’s native tools to:
- Log when the Discord block is executed (via Submissions)
- Tag responses using the Set Variable or Tag blocks
- Combine with Google Sheets or Zapier to log historical messages and filter by type
Final Thoughts
With the Discord block, you can extend your agent’s power beyond just user-facing interactions. It becomes a backend automation tool for your internal teams.
📣 From customer leads to support alerts — let your team know instantly, in the tools they already use.