> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/automations/triggers/external-webhook.md).

# External Webhook

Learn about how to trigger workflows via a Webhook URL

One option to trigger workflows is through a Webhook URL. This is set up slightly differently than other triggers, as it is triggered from outside the platform. 

### How to trigger a workflow via webhook 

Instead of configuring the trigger in the builder itself, you configure external webhook triggers in a workflow's settings. 

{% stepper %}
{% step %}

### Go to workflow settings

Choose the workflow you want to trigger via webhook from the automation list. Go to the Workflow's settings; this is found under the **Settings** tab when modifying a workflow. 
{% endstep %}

{% step %}

### Enable and configure webhook settings

Check the box to **Enable webhook.** This will generate a Webhook URL that uses the POST method. You can also protect with an Access token. 

{% hint style="info" %}
Requests with an access token must include 'Authorization: Bearer **< token> '.**
{% endhint %}
{% endstep %}

{% step %}

### Add the webhook in your external platform

Go to the platform that you want to use to trigger the Couchdrop workflow and find a webhook option. Enter the Webhook URL from Couchdrop.&#x20;
{% endstep %}
{% endstepper %}

#### Turning off other trigger methods

If you are exclusively using an external webhook as a trigger, you can set the automation trigger as scheduled with **Never** and set the Automation to Enabled.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/automations/triggers/external-webhook.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.