Skip to main content

​
1 What it does

Webhooks let systems push data to each other — when something you care about happens upstream, data lands automatically. The webhook URL is the delivery address that ensures data arrives in time.
  • Note: webhooks are an advanced developer feature — work with a developer to set them up.
⚠️ Keep your webhook URL private — never publish it on external sites. Leakage could flood your org with malicious traffic, exhausting developer resources and putting the org at risk.

​
2 Use cases

By setting up a webhook, you can “subscribe” to updates from a system or app:
  • Internal system data sync — set up webhooks in ERP, CRM, etc. to sync data between systems without manual handoff.
  • Website content updates — set up webhooks on watched sites; new content notifies you instead of you reloading the page.
  • Monitoring and alerts — set up webhooks in a monitor or alert platform for real-time health insight and faster incident response.

​
3 How to use

​
3.1 Set trigger keywords

The flow only fires when received data contains a keyword. Click Add keyword to add up to 10 — any one match triggers the flow.

​
3.2 Set the parameter format

When data lands from the upstream system, params pass downstream. Format determines how downstream steps parse and reference these params.

​
3.2.1 Format = JSON

Downstream steps parse params as structured JSON. Fill in a sample payload so subsequent steps can reference structured data.

​
3.2.2 Format = Text

Downstream you reference the whole param block as text. (Special case: if the params match the DingTalk bot message structure, in Send message to this group you can switch Source to Source-data parsing and the params auto-render as a message body.)

​
3.2.3 Format = None

Downstream cannot reference these params.

​
3.3 Configure the webhook URL

Click Copy and paste the URL into the upstream system. (Each automation has its own webhook URL — keep it private; leakage can flood your org with malicious traffic and exhaust developer resources.)

​
3.4 Send an HTTP request

A request triggers the automation.
ParameterValueExample
MethodPOST-
URLThe webhook URL from the triggerhttps://connector.dingtalk.io/webhook/flow/xxxxx
BodyJSON — must contain the trigger keyword to fire{ “key”: “value” }

​
4 Headers and example

NameTypeRequiredDescription
AuthorizationstringNoCredential check (Bearer token) — pass via the Authorization header. Format (case-sensitive): —header ‘Authorization: Bearer \[real Bearer token]’ Single quotes are part of the actual header. Brackets are placeholders only — do not type them. The header key is fixed as Authorization; the value has fixed prefix Bearer. Note the required space between Bearer and the actual token.
Client-TokenstringNoIdempotency. Header key is fixed as Client-Token; value is user-generated, typically a UUID. Empty value = a new request. Non-empty = idempotent update — within 3 hours, the same value triggers only once.
Bearer token example (brackets are placeholders — do not type them): 
curl --location --request POST '[real webhook URL]' \
--header 'Authorization: Bearer [real Bearer token]' \
--header 'Content-Type: application/json' \
--data-raw '{[real request body]}'

​
5 Request body

Set per your needs — must be valid JSON.

​
6 Response and example

Non-zero code in the response means failure. When code is non-zero, look up the message in the error-code table below to debug. Successful response: 
{
"msg": "",
"data": { },
"code": 0
}
Error response: 
{
"data": { },
"code": 800004509,
"msg": "webhook trigger workflow is disabled"
}

​
7 Error codes

When a webhook trigger errors, check the response from the sender side and look up the code below.
CodeMessageCauseFix
800005649Credential check failedCredential check is on, but the credential in the request doesn’t match the one configured in the automation.Re-check and re-enter the credential.
800005650IP not in the allow-list — please checkIP allow-list is on, and the sender IP is not on the list.Add the IP to the allow-list, or send from an allow-listed IP.
800005647Request body too large — please reduceThe webhook request body exceeds 4 MB.Reduce the body size.
800005646HTTP node calls itself, causing a loop — change the HTTP node URLThe trigger is “When webhook fires” and the action is “Send HTTP request” with the HTTP URL set to the same webhook URL — causing a loop.Change the URL in Send HTTP request so it differs from the webhook URL.
800005652Too many requests — try again laterThe webhook receive frequency exceeded the limit and got throttled. - Per AI Table: 50 req/s. - Per single automation: 5 req/s. - Automations without credential check (Bearer token): 1 req/s.Try again later.
800006003Body doesn’t match JSON spec — please fix and retryUsually happens when “set output by sending a request” is used and the body has invalid JSON.Re-check and fix the JSON.

​
8 Use it in practice

  1. As a F&B admin, you want internal goods data synced to a DingTalk group. In Sample params, manually fill the upstream payload (new product name, spec, tea base, ingredients). In Send message to this group, customize the body and use + to reference these params — fresh product details land in the group right away.
  2. If you’ve used “Custom bot” in a chat group before and the upstream params match the DingTalk bot message structure, in Send message to this group switch Source to Source-data parsing and pick the webhook node’s “On data received” output as the source — the params auto-render as the message body and send.