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
WhatsApp Hub (NooviConnect) → Hub Report
AI-generatedSummary
Retrieve a report for a specific NooviConnect-enabled WhatsApp inbox under a given NooviChat account.
Inputs
- Account ID (required) — The NooviChat account ID to specify which account's data to access. Supports expressions for workflows involving multiple accounts.
- Inbox ID (required) — The identifier of the NooviConnect-enabled inbox (an API channel configured with NooviConnect) for which the report is to be generated.
Output shape
A single report object containing analytical or summary data about the specified WhatsApp Hub inbox.
Both 'Account ID' and 'Inbox ID' are required inputs. The operation queries the API endpoint
/noovi_connect/:id/hub_reportscoped by the inbox ID. The exact structure of the returned report depends on the backend implementation and is returned as JSON. There is no pagination or list; the output is a single report per invocation.