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
Pipeline Automation → Update
AI-generatedSummary
Update a pipeline automation in the specified account by automation ID. Send only the fields to change; the flow is validated by the server before saving.
Inputs
- Account ID (required) — NooviChat account ID; supports expressions for multi-account workflows.
- Automation ID (required) — ID of the pipeline automation to update.
- Fields — Optional fields to update: actions and conditions (JSON arrays), active status, description, flow graph (JSON), name, pipeline ID, schedule configuration (JSON), legacy trigger (JSON), or trigger type (event, manual, scheduled, or webhook). Enabling an automation without flow nodes is rejected by the server.
Output shape
A single API response record for the updated automation.
The operation sends the selected fields in the pipeline automation request body. The server validates the flow before saving; invalid updates return an API error.