Actions264
- Conversation Actions
- Message Actions
- Contact Actions
- Inbox Actions
- Agent Actions
- Team Actions
- Label Actions
- Canned Response Actions
- Custom Attribute Actions
- Webhook Actions
- Pipeline Actions
- Card Actions
- Create
- Get
- Get Many
- Update
- Delete
- Move to Stage
- Reopen
- Get Timeline
- Bulk Move
- Get Lead Score
- Recalculate Lead Score
- Add Contact
- Remove Conversation
- Export (CSV)
- Get Import Template (CSV)
- Get Discarded
- Restore
- Delete Permanently
- Assign Owner
- Bulk Assign Owner
- Bulk Set Priority
- Override Lead Score
- Get Attachments
- Delete Attachment
- Follow-up Actions
- Activity Actions
- Lead Scoring Actions
- Campaign Actions
- SLA Actions
- WAHA Actions
- WhatsApp Template Actions
- Appointment Actions
- Professional Actions
- Service Actions
- Partner Actions
- Broadcast Actions
- Broadcast Blacklist Actions
- Commercial Analysis Actions
- Sequence Actions
- WhatsApp Hub (NooviConnect) Actions
- Captain AI Actions
- UAZAPI Actions
- Company Actions
- Pipeline Automation Actions
- Pipeline Webhook Actions
- Pipeline Follow-up Rule Actions
- Sequence Definition Actions
- Activity Template Actions
- Product Actions
- Opportunity Actions
- Follow-up Automation Actions
Sequence → Start (External)
AI-generatedSummary
Starts an active activity sequence on a pipeline card through the external-start endpoint. Provide the card ID, an active sequence definition ID, and optionally a JSON object with external-source context.
Inputs
- accountId (required) — NooviChat account ID; supports expressions for workflows serving multiple accounts.
- cardId (required) — ID of the pipeline card to attach the sequence to.
- definitionId (required) — ID of an active activity-sequence definition to start on the card.
- context — JSON object from the external source; defaults to {}. Only trigger_source, metadata, external_id, source_url, and notes are persisted. Put other data under metadata. A non-object value returns HTTP 400.
Output shape
A single API response record describing the started sequence.
Requires the pipeline_sequences operational account authorization. A card can have only one active or paused sequence for a given definition; attempting to start a duplicate returns HTTP 422. Only the listed context keys are persisted; other top-level keys are silently dropped.