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 Definition → Update
AI-generatedSummary
Update an existing sequence definition in NooviChat by specifying its account ID and sequence definition ID, optionally modifying its name, description, activation status, steps, and trigger settings.
Inputs
- Account ID (required) — NooviChat account ID; supports expressions for multi-account workflows.
- Definition ID (required) — Identifier of the sequence definition to update.
- Additional Fields — Optional fields to update such as name, description, active status, sequence steps (JSON array), trigger type, and trigger conditions (JSON object).
Output shape
a single updated sequence definition record reflecting the applied changes
The operation expects the sequence definition ID and account ID; fields within Additional Fields are optional and overwrite existing values if provided. JSON inputs for steps and trigger conditions must be valid and replace existing data. No explicit pagination applies.