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
Activity → Create From Template
AI-generatedSummary
Create a new activity in NooviChat by duplicating an existing activity template and optionally overriding specific fields.
Inputs
- Account ID (required) — NooviChat account ID. Supports expressions for multi-account workflows.
- Pipeline Card ID (required) — ID of the pipeline card to which this activity will be assigned.
- Template ID (required) — ID of the activity template to copy from.
- Overrides — Optional field values to override those copied from the template, including Assignee ID, Description, Due At, Scheduled At, and Title.
Output shape
a single activity record representing the newly created activity based on the template with applied overrides
The activity creation request is made with the 'pipelineCardId' as a query parameter and the overridden activity fields wrapped inside an 'activity' key in the request body. If no overrides are specified, the template's values are used as is.