The TrustPager API and MCP server both let you fire an automation programmatically — useful when an external system needs to kick off a workflow, or when an AI agent needs to trigger a sequence in response to something happening outside the CRM.
How it works
Every automation in TrustPager has its own unique ID. You fire it by sending a POST request to that automation's endpoint, along with any data the automation's trigger needs to do its job — contact IDs, form values, event details, and so on.
If an automation has multiple triggers configured, each trigger has its own type and expected payload shape. When firing programmatically, you pass the trigger_data that matches whichever trigger type you want to activate — the automation fires when any one of its configured triggers is matched.
The automation runs exactly as if it had been triggered normally: all configured actions execute in sequence, the run is logged, and the full audit trail is available in https://app.trustpager.com/automations.
Triggering via the REST API
The endpoint is:
POST /api/v1/automations/{automation_id}/trigger
Pass your trigger data in the request body:
curl -X POST https://api.trustpager.com/v1/automations/aut_abc123/trigger \n -H "Authorization: Bearer tp_live_xxxxxxxxxxxx" \n -H "Content-Type: application/json" \n -d '{
"trigger_data": {
"contact_id": "{{contact_id}}",
"form_id": "{{form_id}}"
}
}'
The fields inside trigger_data depend on which trigger type the automation uses. Use the schema endpoints (below) to see exactly what each trigger expects.
On success the API returns the automation run ID, which you can use to poll the run status or retrieve logs.
Triggering via the MCP server
If you're building an AI agent with MCP access, use the trigger_automation tool:
trigger_automation(
automation_id: "aut_abc123",
trigger_data: {
"contact_id": "{{contact_id}}"
}
)
The tool returns the same run ID as the REST API and uses the same credit rules — most automation triggers are free to fire.
Finding your automation IDs
Each automation's ID is shown in the URL when you open it in the builder at https://app.trustpager.com/automations. You can also list all automations via the API at GET /api/v1/automations or using the list_automations MCP tool.
Discovering trigger schemas via the API
Before building a trigger call, you can ask the API what fields each trigger type expects — no guessing required.
List all trigger types with sample payloads and {{variable}} tokens:
GET /api/v1/schemas/triggers
This returns every available trigger type along with a sample payload and the variable tokens you can use in trigger_data. This endpoint is free (0 credits).
Get the schema for a specific trigger type:
GET /api/v1/schemas/triggers/{trigger_type}
# Example:
GET /api/v1/schemas/triggers/facebook_lead_ad
Returns the full schema for that trigger — field names, types, which are required, and example values.
Via MCP: use list_trigger_schemas to see all trigger types, or get_trigger_schema(trigger_type: "facebook_lead_ad") to fetch a single schema. Both are free.
Run history and audit trail
Every programmatic trigger is logged in https://app.trustpager.com/automations alongside manually triggered runs. You can filter by automation, status, or date range to see exactly what fired and what the outcome was.
Tip: Use the schema endpoints to validate your trigger_data shape before firing — especially for integrations where the data structure is coming from an external system.
