> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/workflows/workflows/trigger-webhooks.md).

# Trigger webhooks

{% embed url="<https://youtu.be/j9Vw20aMVH8>" %}

We often want to save our team time through automations by sending information to difference platforms we use.

In this video, we'll talk through how to trigger webhooks via Noloco Workflows to send data to third party tools. In this particular example, we'll automate sending information to Stripe via Zapier using Noloco workflows to trigger a Zapier webhook.

#### Setup 'Trigger a Webhook' action

Trigger an outgoing webhook, useful for triggering instant Zaps

The only field you need to specify is the outgoing webhook URL (make sure it starts with https)

<figure><img src="/files/dgDieUGZOrkLAG4SwKU2" alt=""><figcaption></figcaption></figure>


---

# 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://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/workflows/workflows/trigger-webhooks.md?ask=<question>&goal=<endgoal>
```

`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.
