Datasets:
roanbrasil
/
devops-gitops-corpus

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
59.1k
VoltAgent creates this route when you add the trigger handler to your agent. The trigger sends HTTP requests to this endpoint when events occur.
:::tip Important
After adding the snippet to your project:
1. Ensure your VoltAgent server is running
2. Check the **"I've added the snippet to my project"** checkbox
3. Click **Continue** to proceed to delivery configuration
:::
### Step 3.2: Configure Delivery Target
After adding the trigger handler code, configure how the trigger will deliver events to your endpoint.
#### General
- **Target Name**: A descriptive name for this target
→ Example: `Airtable trigger handler`
#### Delivery
- **Destination**
Choose where VoltOps should send trigger events. You have three options:
- **Agent Servers**
Registered servers appear here with their name and URL. Select a server to send trigger events to it.
To register a new server, click **Create Agent Server** and provide:
- **Name**: A name for your server (e.g., `Production server`)
- **URL**: The root URL of your VoltAgent server (e.g., `https://your-deployed-voltagent-server.com`)
- **Tags** (optional): Organize your servers with tags
:::tip
For local development, see the **Volt Tunnels** section below to expose your local server.
:::
- **Volt Tunnels**
[Volt Tunnels](https://voltagent.dev/deployment-docs/local-tunnel/) expose your local development server to the internet via a secure HTTPS connection. Use this to test triggers against your local VoltAgent instance without deploying to a remote server.
This section shows your active local tunnels. If you don't have an active tunnel yet, click **Start Local Tunnel** to open a setup modal.
The modal displays the command you need to run in your terminal. Once you run the command, the modal enters a waiting state with a loading indicator.
```bash
pnpm volt tunnel 3141
```
This gives you a secure HTTPS URL such as `https://happy-cat-42.tunnel.voltagent.dev`. Use it as the delivery target.
:::note
When your tunnel becomes active, it appears in the destination dropdown. Core+ users receive permanent tunnel URLs with custom usernames, while free tier users get random temporary URLs.
:::
- **Custom HTTPS URL**
Select **Custom HTTPS URL** to send trigger events to your own webhook endpoint.
**HTTPS URL**: Enter the URL where you want to receive trigger events (e.g., `https://your-webhook.endpoint`). VoltOps forwards the trigger payload to this address with retries and error tracking enabled.
**HTTP method**: Choose the HTTP method for the request. Select POST (default), PUT, or PATCH depending on your webhook endpoint requirements.
After selecting a destination, configure the endpoint path where your trigger handler is registered.
##### **Endpoint Path**
Specify the path where VoltAgent listens for this trigger:
- **Default**: `/triggers/airtable/recordCreated` (generated based on provider and event)
- You can change this if your handler uses a different path
:::tip
VoltAgent listens on this route when you add the trigger handler to your agent configuration. Keep it unless you've customized your server routing.
:::
:::note **Test Connection**
After configuring your delivery destination and endpoint path, click **Test Connection** to verify your endpoint is accessible.
**Possible results:**
- **Endpoint is responding correctly**: Your endpoint is ready to receive triggers
- **404 Not Found**: The endpoint doesn't exist. Verify you've added the trigger handler to your VoltAgent project
- **Connection failed**: The request failed with an error message. Ensure your VoltAgent server is running and accessible
:::
##### **Delivery Preview**
Below the test connection area, you'll see a preview of the final delivery configuration showing the complete URL and HTTP method that VoltOps will use to send trigger events:
```
POST {destination-url}{endpoint-path}
```
For example: `POST http://localhost:3141/triggers/airtable/recordCreated`
Verify this matches your expected endpoint before saving.