> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/webhook-tools.md). # Connect other tools with webhooks Use webhook intake and outbound webhook steps when a tool does not have a native Distro action. ## Start a Distro workflow Create a **Webhook/API** workflow, define the expected input fields and publish it. From your trusted server, call the authenticated workflow trigger endpoint with a stable idempotency key. Use [Start a workflow](/developers/start-workflow.md) for the endpoint and authentication. Do not place a private API token in browser JavaScript. ## Send data to another tool Add an outbound **Webhook** step. Set the destination, method, headers and supported body mappings. The receiving service must accept that request shape and its authorization. Map the lead identifier, result and event reference the destination needs. Inspect its response and failure branch before publication. ## Use an automation service A service such as Zapier, Make or a custom integration can receive the outbound request or call Distro's API. This is a generic webhook connection, not a promise that Distro includes a native action for every service's product. ## Verify Simulate mappings, then send one controlled live event. Check both the Distro step and the destination record. Avoid repeating a successful destination write merely because a later step failed. See [API errors and retries](/developers/errors.md) for retry discipline. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/webhook-tools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.