Triggers & webhooks

Triggers let Trame start a workflow when something happens in a connected system (e.g., new ticket, message received, record updated). You can also run workflows manually for tests or urgent actions.

How triggers work

Trame supports multiple trigger types to start workflows automatically:

Trigger Types

1. Composio Event Triggers: Real-time events from connected integrations (Slack messages, email, CRM updates)
2. Custom Webhooks: HTTP endpoints for external systems to trigger workflows directly
3. Manual Execution: On-demand workflow execution from the dashboard interface

Event Processing Pipeline

1. Event Reception: Incoming events from Composio integrations or webhook endpoints
2. Workflow Matching: Events are matched to workflows based on trigger configuration
3. Status Filtering: Only Pilot/Live workflows process trigger events (Draft/Paused are ignored)
4. Approval Routing: Pilot workflows pause for human approval before execution
5. Execution Start: Approved or Live workflow execution begins with event data as input

Webhook Integration

• Each workflow automatically gets a unique webhook endpoint (e.g., /api/hooks/invoice-processor-k3m9)
• External systems can trigger workflows via HTTP POST requests to these endpoints
• Optional webhook secrets provide HMAC signature verification for security
• Request payloads become available as input data during workflow execution

Adding a trigger to a workflow

1. Connect the toolkit under Connectors.
2. In Workflows, open or create a workflow and choose a trigger from the available list.
3. Save the workflow. Trame registers the trigger and begins listening for events.
4. Run a manual test first to confirm the workflow works before relying on events.

Manual runs vs. triggered runs

• Manual: Start from the workflow detail page. Great for smoke tests and one-off actions.
• Triggered: Fire automatically from the connected system. Ensure the workflow is Pilot/Live and approvals are configured as needed.

Status interaction

• Draft: Trigger events are ignored; manual runs require approval.
• Pilot: Trigger events start the workflow but pause for approval before executing.
• Live: Trigger events run immediately without approval.
• Paused: All trigger events are ignored until resumed.

Reliability tips for integrators

• Keep connectors healthy; a trigger cannot fire without an active connection.
• Use Pilot first so humans can approve early runs before moving to Live.
• If events stop arriving, verify the workflow status, connector status, and that the trigger is still registered in the source system.
• For security-sensitive sources, pair triggers with workflow-required details (IDs, allowed senders) to prevent acting on untrusted events.