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 → Complete Step
AI-generatedSummary
Send a request to complete the current step in a running sequence attached to a specific pipeline card within a NooviChat account.
Inputs
- Account ID (required) — Numeric ID of the NooviChat account; supports expressions for workflows involving multiple accounts.
- Card ID (required) — String ID of the pipeline card that the sequence is attached to.
- Sequence ID (required) — String ID of the sequence execution currently running on the specified card.
Output shape
a JSON object representing the updated state of the sequence after the completion of the step
The operation targets a specific sequence execution on a card within an account and completes the current step. It requires the three identifiers: accountId, cardId, and sequenceId. The response structure depends on the API's return for the completion action but typically includes details about the sequence progression or status.
Examples
Example 1: Completing a step of a sequence attached to a pipeline card
Provide the account ID, the card ID where the sequence is attached, and the sequence execution ID. The operation completes the current step in that sequence, allowing workflow automation to progress to the next step or update the sequence status accordingly.