Actions113
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
Overview
This node allows updating an integration hook within a specified account. Integration hooks are typically used to connect external services or automate workflows by triggering actions when certain events occur. This node is beneficial when you need to modify the configuration or settings of an existing integration hook, such as changing callback URLs, authentication parameters, or other integration-specific options.
Practical examples include:
- Updating webhook URLs for third-party integrations.
- Changing authentication tokens or credentials used by the integration.
- Modifying event subscriptions or payload formats in the integration settings.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the integration hook exists. |
| Hook Id | The numeric ID of the specific integration hook to update. |
| Settings | A JSON object containing the new settings required by the integration hook. This can include any configuration parameters needed by the integration. |
Output
The node outputs JSON data representing the updated integration hook details after the update operation completes successfully. This output typically includes confirmation of the changes made and the current state of the integration hook.
If the integration supports binary data (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing the integrations.
- The base URL for the API is configured via credentials.
- The node uses HTTP requests with JSON payloads to interact with the external API.
Troubleshooting
- Invalid Account Id or Hook Id: If the provided IDs do not exist or are incorrect, the API will likely return an error indicating that the resource was not found. Verify the IDs before running the node.
- Malformed JSON in Settings: Since the
Settingsproperty expects valid JSON, ensure the input is correctly formatted. Invalid JSON will cause parsing errors. - Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update integration hooks.
- Network Issues: Connectivity problems may cause request failures; verify network access to the API endpoint.
Links and References
- Refer to the external service’s API documentation for detailed information on integration hooks and their settings.
- JSON formatting guides to help construct valid
Settingsinput.