> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/operate/operate/triggers/using-a-webhook-trigger.md).

# Using a webhook trigger

Call a webhook trigger from your backend once it exists, with an example curl.

Once the webhook trigger is built, in the dashboard, with Build with AI or with your AI tool, it can be called as shown by the example curl below. The first ID in the URL is your organization's ID.

```bash
curl --location 'https://webhooks.fastn.dev/prod/triggers/<ORG_ID>/webhooks/<WEBHOOK_ID>' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <YOUR_API_KEY>' \
--data '{
}'
```

The `x-api-key` header is needed only when the trigger's auth is set to API key. A trigger with no auth accepts the call without it.

The key is your `fsk_` key, in `x-api-key`, as `Authorization: Bearer fsk_…` (the way the [platform API](https://docs.fastn.ai/reference/api.md#authentication) takes it), or in the older `x-fastn-access-key`.

On a trigger whose auth is API key, your backend can also name the customer and end user the call is for with the optional `x-org-id` and `x-user-id` headers, proven with `x-identity-hmac` (computed as in [API keys](https://docs.fastn.ai/embed/api-keys.md#identity-hash)). These headers name the customer only when your API key's identity verification is set to Monitor only or Enforce, or when the call carries `x-identity-hmac`. A key set to Enforce refuses the call unless they come with a valid hash. Otherwise, and on a trigger with no auth, those headers are passed through to the workflow as ordinary headers.


---

# 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.fastn.ai/operate/operate/triggers/using-a-webhook-trigger.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.
