Developers
Diamonds

List triggers

GET/automations/diamond/{diamond_id}/triggers

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.

Authorization

AuthorizationBearer <token>

Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.

In: header

Path Parameters

diamond_id*string

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/automations/diamond/string/triggers"
{  "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"    }  ],  "page": {    "limit": 1,    "next_cursor": "string",    "prev_cursor": "string"  }}

Update a stage PATCH

Updates the waiting interval of a time-based stage. Only time-based stages accept an interval, and only the supported interval values are accepted. The change applies to future scheduling; communications already scheduled for leads are not affected. Stages share the Diamond's revision: send the Diamond's current `ETag` in the `If-Match` header to avoid overwriting a newer version.

Ensure a stage trigger POST

Ensures 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.