Update event trigger
Update an existing event trigger on the specified agent. Only the fields supplied in the request body are changed; omitted fields keep their current value. Use enabled to pause (false) or resume (true) the trigger. As with creation, non-fatal prerequisite gaps are returned in the warnings array rather than failing the request.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the agent that owns the event trigger.
The ID of the event trigger to update.
Body
Fields to update on the event trigger. Only supplied fields change; omitted fields keep their current value. trigger_source is set at creation and cannot be changed — to switch providers, delete the trigger and create a new one.
Set to true to resume the trigger; false to pause it.
Updated event in "ResourceName:eventType" format. Omit to leave the current event unchanged.
255Updated name. Pass null to clear.
255Updated description. Pass null to clear.
1000Updated run conditions. Pass null to clear.
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
Updated 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.