Ensure a stage trigger
/automations/diamond/{diamond_id}/triggersEnsures that the trigger for a given stage exists. Every stage already has a trigger when the Diamond is created, so this operation normally returns the existing trigger; it creates a new one only if the stage's trigger is missing.
Changes to triggers affect future communications with leads.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Header Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/automations/diamond/string/triggers" \ -H "Idempotency-Key: string" \ -H "Content-Type: application/json" \ -d '{ "stage_id": "string" }'{ "data": { "channel": "http", "created_at": "2019-08-24T14:15:22Z", "destination": { "email": "string", "phone": "string", "url": "string" }, "diamond_id": "string", "enabled": true, "event_type": "string", "id": "string", "object": "trigger", "revision": "string", "stage_id": "string", "updated_at": "2019-08-24T14:15:22Z" }}List triggers GET
Returns the triggers of the Diamond, one per stage. Destinations are masked: only the URL host or the last digits of the phone number are returned.
Retrieve a trigger GET
Retrieves a trigger of the Diamond. The destination is masked in the response. The response includes an `ETag` representing the current revision. Send this value in the `If-Match` header when updating the trigger to avoid overwriting a newer version. Only triggers that belong to the Diamond in the path can be retrieved.