A workflow driven by a webhook trigger cannot retrieve the body content.

[LHB6540]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I've built a webhook-triggered workflow that attempts to read the doc_content and requests fields from the workflow body.

Using the test run button in the upper right corner of the interface, it works correctly and retrieves the content.

curl --location 'http://localhost/triggers/webhook-debug/ZYlhgDYZ2cnyJQi1sq06u8ic' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer app-UlzE41aTkjNN1qY9U0qLTeQ9' \
--data '{
  "doc_content": "updateInfo：20251216215706 - clientVersion：202512301554153",
  "requests": "{\"version\": 20251216215706}"
}'

However, after publishing the workflow and calling it via the workflow API, I found that the webhook is receiving empty input, causing subsequent workflow nodes to behave unexpectedly.

curl --location 'http://localhost/v1/workflows/run' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer app-UlzE41aTkjNN1qY9U0qLTeQ9' \
--data '{
    "inputs": {
        "doc_content": "updateInfo：20251216215706 - clientVersion：202512301554153",
        "requests": "{\"version\": 20251216215706}"
    },
    "user": "dify"
}'

{
    "task_id": "5865f0a6-fee7-47dc-a335-f8f598bd547c",
    "workflow_run_id": "29d9f6d6-135f-4f67-9386-c8e58806ba05",
    "data": {
        "id": "29d9f6d6-135f-4f67-9386-c8e58806ba05",
        "workflow_id": "88dd48fa-4b61-4975-bdc9-338624af7997",
        "status": "succeeded",
        "outputs": {
            "text": "{\n  \"result\": {\n    \"response\": {\n      \"code\": 1,\n      \"msg\": \"without given info, can't not compare\"\n    }\n  }\n}"
        },
        "error": null,
        "elapsed_time": 2.074854,
        "total_tokens": 206,
        "total_steps": 3,
        "created_at": 1769482074,
        "finished_at": 1769482076
    }
}

I want to check if there are any errors in my request body. I think my current request body has been formatted according to the documentation.

2. Additional context or comments

No response

[dosubot[bot]]

Hi @LHB6540! I'm Dosu and I’m helping the dify team.

The root cause is that in published workflows, the webhook trigger node expects its input fields (like doc_content and requests) to be nested inside a webhook_data.body object, not at the top level of the inputs map. In test/debug mode, the system injects your raw fields directly, but in production, it requires this extra wrapping for the node to see the data you send (source).

To fix this, structure your API call like this:

{
  "inputs": {
    "webhook_data": {
      "body": {
        "doc_content": "updateInfo：20251216215706 - clientVersion：202512301554153",
        "requests": "{\"version\": 20251216215706}"
      }
    }
  },
  "user": "dify"
}

This way, the webhook node will correctly extract doc_content and requests from the incoming request (source).

If you still see empty inputs, double-check that your workflow is deployed (not just in draft), the webhook trigger is enabled, and the HTTP method/content-type matches your node configuration (source).

This input wrapping requirement is not always obvious in the documentation, so it's a common stumbling block.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[dosubot[bot]]

You're right—there is currently no official Dify documentation that explains the required input format for webhook-triggered workflows in published mode. This is a known documentation gap and has been acknowledged by the maintainers as something they're working to improve, but as of now, the API reference does not cover this case (source).

The reason your published workflow receives empty inputs is that, in production, the webhook node expects its fields (like doc_content and requests) to be nested inside webhook_data.body within the inputs object. This is different from test/debug mode, where the fields are injected directly (source, source).

Here’s a working example for the /v1/workflows/run API:

{
  "inputs": {
    "webhook_data": {
      "body": {
        "doc_content": "updateInfo：20251216215706 - clientVersion：202512301554153",
        "requests": "{\"version\": 20251216215706}"
      }
    }
  },
  "user": "dify"
}

If you use this structure and still see empty inputs, double-check that your workflow is published (not in draft), the webhook trigger is enabled, and your request’s HTTP method and content-type match the node’s configuration (source). You can also check logs in the worker container for more details.

Until the documentation is updated, this manual wrapping is required for published webhook workflows to receive input data.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[LHB6540]

The problem remains unresolved, and the provided answers have not changed.

[LHB6540]

How can I seek help from non-robots?

[LHB6540]

I understand what's going on.
Webhook triggers provide dedicated endpoints for triggering workflows, rather than using the workflow API.
However, the "Access (Request) API" instructions accompanying each workflow interface can easily mislead users into thinking that this method can be used to drive workflows. In fact, workflow API access is only applicable to workflows that begin with "user input" type input.