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

# Webhooks

Use Smartrr's webhooks to build automations like email campaigns, tag customers and more.

{% hint style="info" %}
**Note:** In order to connect your receiving application to Smartrr, you will need the webhook url provided by that application. Please refer to that application’s help documentation regarding webhook urls.
{% endhint %}

### What are webhooks?

Webhooks are automated messages sent between apps when something happens. They are useful as standalone alerts or to use as triggers for another action. They contain a message – or payload – in the form of a url.

### How do you use webhooks in Smartrr?

Within the Smartrr app, navigate to **Integrations** under CONFIGURATION in the left-hand menu. Click **Add Webhook**.

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2FeMJcv8xTBi94u9dqny2x%2Fwebooks.png?alt=media&amp;token=60d7cda7-a735-47a8-9a5b-c27b0721dd6a" alt="The webhook settings are found under the &#x22;Integrations&#x22; menu. It&#x27;s tab is right next to the &#x22;API Keys&#x22; tab."><figcaption></figcaption></figure>

You can link your webhooks to any of the following subscription events:

* Subscription activate&#x20;
* Subscription cancel
* Subscription create&#x20;
* Subscription failed payment
* Subscription gift
* Subscription pause
* Subscription send now&#x20;
* Subscription next send date
* Subscription skip&#x20;
* Subscription successful payment&#x20;
* Subscription un-skip
* Subscription upcoming order
* Payment method update

Within the field labeled **URL**, enter the URL of the receiving application, then select which event you’d like your webhook to listen for.

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2FmSbZKff7n8uQAzwaNeOr%2FScreenshot%202024-04-13%20at%206.39.53%E2%80%AFPM.png?alt=media&amp;token=832dd05e-5426-4076-863b-2f93f87a041d" alt="When adding a webhook, you only need to do 2 things: choose your Smartrr related trigger from the dropdown list and add the URL for the app that would be listening for this trigger. Not sure what to do here? Contact the support team for the app that you&#x27;re looking to set up this webhook for."><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 by asking a question.

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

```
GET https://help.smartrr.com/docs/support/integrations/webhooks.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.