How to integrate Unify with Discord
To integrate Unify with Discord, send a POST request from a Unify Play to the tool’s configured webhook trigger and map the received fields into the intended action. Use this connection to post a focused prospect review alert in Discord.[1][2][3]
- Connection
- Via webhook
- Team collaboration
- Tool
- Discord
- Discord
- Data flow
- Unify → Discord
- JSON payload
At a glance
- Via webhook: Discord receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Test mention handling
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
An alert should answer who needs attention and why now. Use the channel as a review surface with a clear audience rather than a raw event log. Keep the message short enough for a teammate to assess without opening several systems.
A good fit when
Teams that want to post a focused prospect review alert in Discord and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Discord operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Business decision | Post a focused prospect review alert in Discord |
| Receiving contract | Agree which of the 1 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Discord request and its resulting action. |
| Completion | Decide who can confirm the Discord outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Post a focused prospect review alert in Discord
Start with one controlled record and one intended Discord outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Discord setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Test mention handling
Test mention handling: send fictional company text containing an @everyone string and confirm the message does not notify the whole server. Keep the payload mention policy unchanged.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Discord against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Post a focused prospect review alert in Discord
Inspect the posted message in the correct channel and verify that no unintended mentions were generated.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Discord.
Do I need a Discord bot for this handoff?
An incoming webhook can post to its configured channel without a bot user. The webhook URL contains the credential used for that posting path.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Discord workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Create an incoming webhook for the intended channel and copy its URL. Check channel visibility before placing prospect information in it.[3] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Discord connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Discord environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Prepare the Discord destination
Create an incoming webhook for the intended channel and copy its URL. Check channel visibility before placing prospect information in it.[3]
Configure the destination action
Send content with allowed_mentions.parse set to an empty array so prospect text cannot create unintended mentions. Use wait=true when checking the message response.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]
Request configuration
- Method
POST- URL pattern
https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN?wait=true- Headers
Content-Type: application/json- Authentication
- The webhook token is embedded in the generated URL. Keep the entire URL secret; this incoming webhook does not require a bot token.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"content": "Review Example Company: Alex Morgan (alex@example.com). Source: Unify.",
"allowed_mentions": {
"parse": []
}
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]
| Payload field | Value to send |
|---|---|
content | Keep the editorial message template and replace only its fictional person name, email, or company name with available source fields. Preserve JSON escaping. If missing: Remove optional missing context from the message; hold it if the receiving team cannot identify the record. |
allowed_mentions.parse | Keep the empty array to disable automatic mention parsing in this Discord example. If missing: Keep this configured value in the request; do not replace it with a blank prospect field. |
Build a short content string from factual fields. Keep mention controls fixed and do not interpret prospect text as a list of user or role mentions.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
The webhook token is embedded in the generated URL. Keep the entire URL secret; this incoming webhook does not require a bot token. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Discord environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Discord resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
