Short answer: Drop the "Salesloft → List Salesloft Cadences" 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 |
|---|---|---|---|
Filter by Sharing shared | options | Optional | Limit to shared (team) cadences or private (personal) ones. |
Owned by User ID owned_by_id | string | Optional | Only cadences owned by this Salesloft user. |
Per Page per_page | number | Optional | Page size, 1–100. Defaults to 25. |
{"shared": "{{trigger.shared}}","owned_by_id": "12345","per_page": "{{trigger.per_page}}"}
{"data": [{"id": 98765,"name": "Q2 Outbound — Enterprise","draft": false,"shared": true,"owned_by": {"id": 12345,"name": "Jane Smith"},"current_state": "active_published"}],"metadata": {"paging": {"per_page": 25,"total_count": 1,"total_pages": 1,"current_page": 1}}}
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.