Trigger Templates
Templates are reusable trigger configurations. Define the logic once — trigger type, actions, parameters — and apply it to any assistant without reconfiguring from scratch. Useful for standardizing integrations across a team or offering ready-made building blocks to clients.
When to use
- The same webhook is called by multiple different assistants
- You want clients to configure only their own parameters (URL, token) without touching the underlying logic
- You need to standardize integrations across assistants in a team
Creating a template
Go to Templates → New and fill in:
Basic information
| Field | Description |
|---|---|
| Name | Template identifier |
| Description | Explains what it does and how to use it |
| Public | Available to all assistants in the company |
| Interpret response | The LLM rewrites the webhook response in natural language before displaying it to the user |
Trigger types
Choose the type of trigger the template will configure:
| Type | Description |
|---|---|
WEBHOOK |
Calls any external HTTP API via POST |
KNOWLEDGE |
Queries the assistant's knowledge base |
NATIVE |
Native platform actions (buttons, images, audio) |
GOOGLE_CALENDAR |
Google Calendar integration |
CHAT_INTEGRATION |
External chat system integration |
CATALOG_INTEGRATION |
Product catalog integration |
CRM |
Native Verboo CRM |
FEEGOW |
Feegow scheduling system |
Actions
Each template can chain one or more actions that execute when the trigger fires. Available actions follow the same trigger types above and run in sequence.
Customizable parameters
Parameters are the fields that users fill in when applying the template to an assistant — for example, the webhook URL or the API token specific to each client.
| Field | Type | Description |
|---|---|---|
| Name | — | Parameter identifier (used by the LLM to call the trigger) |
| Type | string, number, boolean, array |
Expected value type |
| Description | — | Explains what the parameter represents |
| Required | — | Whether the field must be filled in |
| Fixed options | — | Restricts values to a predefined list (enum) |
Parameters are automatically converted to JSON Schema and used by the LLM to understand how and when to call the trigger.
Public vs. Private
| Public | Private | |
|---|---|---|
| Visible to | All company assistants | Creator only |
| Editable by | Admin or creator | Creator only |
| Best for | Team standards and shared integrations | Project-specific configurations |
See Triggers to understand how triggers work inside an assistant.