> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/troubleshooting-process-flows/process-flow-error-when-using-a-webhook-connector.md). # Process flow error when using a webhook connector ## Scenario Your process flow includes a connector which is attempting to hit a webhook and the following error is displayed: ```html An Error Occurred: Unprocessable Content

Oops! An Error Occurred

The server returned a "422 Unprocessable Content".

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

``` ## Reason This error can occur if: * The webhook connector does not include a `content-type` header * The process flow is not enabled ## Solution * Check the connector setup and ensure that header options include a `content-type` header. For more information see [Connector builder header options](/product-documentation/developer-hub/connector-builder/building-your-own-connector/4-endpoints/endpoint-options/header.md#webhooks). * Ensure that the process flow being run is enabled. For more information see [Enabling & disabling a process flow](/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.wearepatchworks.com/product-documentation/process-flows/troubleshooting-process-flows/process-flow-error-when-using-a-webhook-connector.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.