Actions58
- Activity Actions
- Company Actions
- Contact Actions
- Deal Actions
- External Property Actions
- Import Actions
- List Actions
- Note Actions
- Pipeline Actions
- Sequence Actions
- Sync Actions
- Task Actions
- Template Actions
- User Actions
Sequence → Search Sequence Details
AI-generatedSummary
Searches for contacts associated with a specified Crono sequence, applying optional filters and sort order. Use the raw JSON option to provide the search request body directly; otherwise, configure the sequence ID and search fields in the node.
Inputs
- API Version — Crono Public API version; defaults to 1.
- Return All — When enabled, requests all results. Otherwise, use Limit and Offset to control the result page.
- Use Raw JSON — When enabled, sends the Search (JSON) value as the search body instead of the structured search fields.
- Search (JSON) — Raw JSON search request body, shown when Use Raw JSON is enabled.
- Additional Fields — Optional field/value pairs to merge into the structured search payload.
- Sequence ID (required) — ID of the sequence whose details to retrieve.
- Text — Free-text filter for sequence details.
- Limit — Maximum results to return when Return All is disabled; defaults to 50.
- Offset — Number of results to skip when Return All is disabled; defaults to 0.
- Sort — Sort order for contacts, last activity, last interaction, progress, or score, ascending or descending; defaults to Contacts Asc.
- Status — Filter by sequence status, such as Active, Answered, Completed, Converted, Dead, Stopped, or Unknown. Any leaves the status filter empty.
- Only Specific Task — Filter by selected task events, including email opens, clicks, replies, bounces, delivered or unopened emails, connected calls, and LinkedIn invitation or message events.
- Only My Sequences — When enabled, limits the search to your sequences.
- Only My Contacts — When enabled, limits the search to your contacts.
Output shape
A list of sequence detail results.
The provided source pack contains only a signature-level view, so it does not expose response extraction or pagination behavior. Result fields and exact pagination behavior are not specified.