List triggers

GET/v1/triggers

List event-driven automations for the authenticated user.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
NameLocationTypeRequiredDescription
environmentIdquerystringNo
sourcequerygithub | slack | email | webhook | cron | customNo
enabledquerybooleanNo
limitqueryintegerNo
offsetqueryintegerNo

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Trigger listapplication/json
FieldTypeRequiredDescription
objectstringNo
dataobject[]No
data[].idstringNoUnique identifier.
data[].userIdstringNoUser ID.
data[].namestringNoHuman-readable name.
data[].environmentIdstringNoComputer ID.
data[].agentIdstringNoAgent ID.
data[].sourcegithub | slack | email | webhook | cron | customNo
data[].eventstringNo
data[].filtersobjectNo
data[].actionobjectNo
data[].action.typesend_messageYes
data[].action.promptstringNoPrompt passed into the trigger execution thread.
data[].action.messagestringNoBackward-compatible alias for `prompt`.
data[].action.templatestringNoLegacy template field. Use `prompt` for new integrations.
data[].enabledbooleanNo
data[].webhookSecretstringNo
data[].webhookUrlstringNo
data[].lastTriggeredAtstringNo
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo
total_countintegerNo
List triggers
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow