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.

​
4 Headers and example

Bearer token example (brackets are placeholders — do not type them):

​
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:
Error response:

​
7 Error codes

When a webhook trigger errors, check the response from the sender side and look up the code below.

​
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.