Triggers
Triggers enable agents to execute in response to external events via webhooks. When something happens in another system -- a form submission, a payment, a code push -- it can automatically invoke your agent.
Why Triggers?
Connect your agents to the outside world:
- Form submissions -- Process new leads instantly
- Payment events -- Handle Stripe webhooks
- CI/CD -- Run agents on deployment events
- Custom integrations -- Any system that can send HTTP requests
How Triggers Work
When an external system sends an HTTP request to your trigger's unique webhook URL, MeetLoyd validates the request, extracts and maps the input data, and executes the assigned agent or workflow with that data.
External System --> Trigger Webhook URL --> Validation & Mapping --> Agent Execution --> Response
Integration Event Registry
MeetLoyd maintains a registry of events from connected integrations. When you connect an integration, you gain access to its events.
| Integration | Example Events |
|---|---|
| HubSpot | Contact Created, Deal Stage Changed, Deal Won/Lost, Ticket Created, Form Submitted |
| Slack | Message Posted, Bot Mentioned, Reaction Added, Channel Created |
| GitHub | Code Pushed, PR Opened/Merged/Closed, Issue Opened/Closed, Release Published |
| Stripe | Payment Succeeded/Failed, Invoice Paid, Subscription Created/Canceled |
Event Categories
Events are organized by category for easier discovery: CRM, Communication, Development, Payment, Support, Calendar, HR, and Task.
Trigger Types
| Type | Description |
|---|---|
| Webhook | External system sends event to MeetLoyd |
| Polling | MeetLoyd periodically checks for changes |
| WebSocket | Real-time bidirectional connection |
| Triggers from email events | |
| Manual | User-initiated triggers |
Trigger Status
| Status | Description |
|---|---|
| Active | Accepting and processing requests |
| Paused | Accepting but not processing (queued) |
| Disabled | Rejecting all requests |
Best Practices
Use input mapping to pull specific fields rather than passing the entire webhook payload. This avoids sensitive data exposure and keeps agent input clean.
Include static fields like source: "stripe" and environment: "production" so your agent knows where the data came from.
Check failed executions regularly. A spike in failures often indicates a webhook format change or authentication issue.
"Stripe Payment Success Handler" tells you everything. "Webhook 1" tells you nothing.
Next: Learn about Workflows for orchestrating multi-step processes.