Trigger journey

/automations/{automation_id}/triggerPOST

The workspace automation must be active and published with an API trigger. Acceptance does not mean all workflow steps have completed. Required scope: automations:write.

Authorization

BearerAuth *Bearer <token>

API key generated under Account Settings → API Keys (rk_live_...). Send as header Authorization: Bearer <key>.

Request Bodyapplication/jsonrequired

contact *object

Show properties

id?integer

external_id?string

external_customer_id?string

email?string (email)

phone?string

phone_number?string

first_name?string

last_name?string

company?string

country?string

city?string

birthday?string

timezone?string

custom_fields?object

data?object

event_id?string

Response

202 · Successful response. See the integration guide for status and lifecycle semantics.

Type: object

401 · Invalid, expired, revoked or missing key.

Invalid, expired, revoked or missing key.

403 · Required scope not granted.

Required scope not granted.

422 · Validation or eligibility failure.

Validation or eligibility failure.

Request example

curl -X POST "https://convert.ruut.chat/api/v1/automations/<automation_id>/trigger" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
  "contact": {
    "id": 0,
    "external_id": "string",
    "external_customer_id": "string",
    "email": "[email protected]",
    "phone": "string",
    "phone_number": "string",
    "first_name": "string",
    "last_name": "string",
    "company": "string",
    "country": "string",
    "city": "string",
    "birthday": "string",
    "timezone": "string",
    "custom_fields": {}
  },
  "data": {},
  "event_id": "string"
}'