Actions129
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts Actions
- Contact Labels Actions
- Conversation Assignments Actions
- Conversations Actions
- Conversation Add Labels
- Conversation Filter
- Conversation List
- Conversation List Meta
- Get Conversation Reporting Events
- Get Details Of A Conversation
- List All Labels Of A Conversation
- New Conversation
- Toggle Priority Of A Conversation
- Toggle Status Of A Conversation
- Update Conversation
- Update Custom Attributes Of A Conversation
- Custom Filters Actions
- Inboxes Actions
- Integrations Actions
- Messages Actions
- Profile Actions
- Reports Actions
- Automation Rule Actions
- Help Center Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Actions
- Audit Logs Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Teams Actions
- Webhooks Actions
- Conversation Actions
Integrations → Create An Integration Hook
AI-generatedSummary
Create a new integration hook for a specified account and app, optionally associated with an inbox, by providing its status and configuration settings.
Inputs
- Account Id (required) — The numeric ID of the account for which the integration hook is created.
- App Id — The ID of the app to which the integration hook belongs.
- Inbox Id — The inbox ID if the integration hook is an inbox-type hook.
- Status — Numeric status to set the integration hook as inactive (0) or active (1).
- Settings — JSON object defining the settings required by the integration.
- Request Options — Collection of HTTP request options such as batching details, SSL validation, proxy settings, and timeout configuration.
Output shape
a single JSON object representing the created integration hook, including its ID and configured properties
The operation returns the integration hook data as stored in the system. Optional fields can be omitted. The status defaults to active (1) if not specified. Settings must be valid JSON. Request options affect the underlying HTTP request behavior but do not affect the output data.