Short answer: Drop the "Salesloft → Salesloft Add Person to Cadence" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Person ID person_id | string | Required | The Salesloft person ID to enroll. |
Cadence ID cadence_id | string | Required | The cadence to enroll the person into. |
Cadence User ID user_id | string | Optional | The Salesloft user who will own the cadence membership. Defaults to the connected user. |
{"person_id": "1234567","cadence_id": "98765","user_id": "12345"}
{"data": {"id": 555666,"user_id": 12345,"added_at": "2026-04-11T10:00:00.000Z","person_id": 1234567,"cadence_id": 98765,"current_state": "active"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.