Sign in
Triggers

Create or update a trigger

Creates a new trigger instance or updates an existing one with the same configuration. Triggers listen for events from external services (webhooks or polling) and can invoke your workflows. If a matching trigger already exists and is disabled, it will be re-enabled. Provide either a connected_account_id to pin a specific user connection, or a user_id to auto-resolve the first active connection for that user and the trigger's toolkit.

post/api/v3/trigger_instances/{slug}/upsert

Path parameters

slugstring required

The slug of the trigger instance. Case-insensitive (internally normalized to uppercase).

The slug of the trigger instance. Case-insensitive (internally normalized to uppercase).

Request body

connectedAuthIdstring connectedAccountId

DEPRECATED: This parameter will be removed in a future version. Please use connected_account_id instead.

triggerConfigobject

DEPRECATED: This parameter will be removed in a future version. Please use trigger_config instead.

connected_account_idstring connectedAccountId

Connected account nanoid. Optional when user_id is provided — the first active connection for that user and the trigger's toolkit is auto-resolved.

user_idstring

The user id (entity id) that owns the connection. When connected_account_id is omitted, the first active connection for this user and the trigger's toolkit is auto-resolved (same as tool execution). When connected_account_id is also provided and the project has 2FA enabled, user_id is validated against the owner of that connection.

trigger_configobject

Trigger configuration

versionstring

DEPRECATED: This parameter will be removed in a future version. Please use toolkit_versions instead.

Example request

{
  "version": "latest"
}

Response

Successfully upserted trigger instance

trigger_idstring required

ID of the updated trigger

Changes

Changed in 1 of the 10 revisions of this API.1