> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.17/voyage-management-system/step-by-step-guides/alerts/webhook-subscriptions/create-webhook-subscription.md).
# Creating a Subscription Template
1. Open the **Subscription Templates** module in the **Alerts** section.
2. Click **Create Subscription Template**in the top right corner.
3. Fill in the required fields (marked with \*) for each step in the dialogue.
4. Click **Create**.
## Create Subscription Template
Below is an example of a Subscription Template with an expression requiring a change of the field bankName and the swift address to equal a number for a notification to be sent. The expression builder allows building complex conditions to limit the amount of notifications to be informative and wanted. \
\
The fields "Template Message" and "Fields" are optional, and can customize the notifications sent.
{% hint style="info" %}
In Expression Builder, the `Field` can be selected with the Customize Columns modal, like in lists. Conditions can be customized in detail using grouping `Add Group` , to allow multiple combinations of `AND` /`OR` conditions. A simplified preview of the conditions are displayed at the bottom of the modal.
{% endhint %}
{% hint style="info" %}
**Fields** limit what fields should be returned in the notification and can look like this {"fieldName1":"\*","fieldName2":"\*"}. Read more about how to specify **Fields** [here](https://api.dataloy.com/dataloy-rest-api/adjust-number-of-fields-to-be-returned-from-a-request).
{% endhint %}
Subscription Templates can either use Object Type, Event Type and an Expression as a "trigger". Or it can use an existing Alert Script to decide when a notification will be sent. You need to clear Object Type and Event Type to be able to change from an Expression to Alert Script.
---
# 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.dataloy.com/release-8.17/voyage-management-system/step-by-step-guides/alerts/webhook-subscriptions/create-webhook-subscription.md?ask=&goal=
```
`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.