> For the complete documentation index, see [llms.txt](https://docs.socializit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.socializit.com/webhooks.md).

# WEBHOOKS

Webhooks allow to send data to external tools like Zapier, Ifttt or others.

In this guide we take Zapier as an example.

* Create a "zap"
* Select "Webhook by Zapier" in Trigger
* Select "Catch hook" in Trigger event
* Click "continue"
* Copy the given webhook URL  

![](/files/-MM4wy7TqJ1HI20RMKN8)

* Click "continue"
* Paste the copied URL in the list's bot setting  

![](/files/-MM4xmuC1JlPdshN8NzB)

* Click on "send test webhook" on Socializit
* On Zapier click on "Test webhook"
* Now you should be able to see the test data  
* You can continue Zapier integration setting up a Google Spreadsheet which will receive data through the webhook ([here](https://docs.google.com/spreadsheets/d/1dKUEEILOFRQylRTF7YuurFpTITNmf-__JjrwzPZ8yuA/edit#gid=0) you can find a model) or other kind of actions as for example email sending

![](/files/-MM4z71W3xso8ZXW_SGm)

 


---

# 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://docs.socializit.com/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.