Create event trigger
Create an event trigger for the specified agent so it runs automatically when the configured provider event fires. Prerequisite gaps that do not prevent the trigger from being saved (e.g. a missing Procore company/project mapping or credentials) are returned in the warnings array on the response rather than failing the request. An agent may only have one event trigger — attempting to create a second is rejected with a 409 error.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the agent to create the event trigger for.
Body
Whether the trigger should be active immediately. Set to false to create it in a paused state.
The external provider that emits the event. Currently only Procore is supported.
procore The event that fires the agent, in "ResourceName:eventType" format (e.g. "Tasks:create"). Required even when enabled is false.
255Optional name for the App Event automation.
255Optional description of what the App Event automation does.
1000Optional natural-language conditions that must hold for the agent to run when the event fires.
3000Controls how the agent's response conversation is threaded when the trigger fires. create_new_thread_each_time starts a fresh thread for every event; when omitted, responses reuse a single thread.
create_new_thread_each_time Response
Created event trigger
The object type, always 'event_trigger'.
event_trigger Unique identifier for the event trigger.
Whether the trigger is active. When false the agent does not run in response to the event until it is re-enabled.
The external provider that emits the event. Currently only Procore is supported.
procore The event that fires the agent, in "ResourceName:eventType" format (e.g. "Tasks:create", "Project Users:update").
User-provided name for the App Event automation.
User-provided description of what the App Event automation does.
Optional natural-language conditions that must hold for the agent to run when the event fires. When null, the agent runs on every matching event.
Controls how the agent's response conversation is threaded when the trigger fires. create_new_thread_each_time starts a fresh thread for every event; when omitted, responses reuse a single thread.
create_new_thread_each_time ISO 8601 timestamp of when the event trigger was created.
ISO 8601 timestamp of the last modification to the event trigger.
Non-fatal issues surfaced while wiring up the trigger (e.g. Procore company/project/credential prerequisite gaps). An empty array means the trigger was configured with no issues. Each entry pairs a stable machine-readable code with a human-readable message.