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 → Create
AI-generatedSummary
Create a Pipeline Automation in the selected account, with a required name and optional automation fields. The server validates the flow graph; creation is refused with HTTP 422 if the automation has no flow nodes.
Inputs
- Account ID (required) — NooviChat account ID; supports expressions for workflows that target multiple accounts.
- Name (required) — Name for the new automation.
- Fields — Optional automation settings: actions and conditions (JSON arrays), active status, description, flow graph (JSON), pipeline ID, schedule configuration (JSON), legacy trigger (JSON), and trigger type (Event, Manual, Scheduled, or Webhook). The collection also exposes a Name field marked for update use; use the required Name field above when creating.
Output shape
A single API response item containing the created pipeline automation.
The flow is validated by the server. A flow with at least one node is required; enabling an automation without flow nodes is also refused with HTTP 422.