Actions113
- 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
- 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
- Webhooks Actions
- Teams Actions
- Custom Filters Actions
- Reports 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 custom settings required by the integration.
Practical examples include:
- Updating webhook URLs for third-party integrations.
- Changing authentication tokens or credentials used by the integration.
- Modifying event filters or payload formats sent by the integration hook.
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 updated fields and may contain metadata about the integration hook's current state.
No binary data output is expected from this node.
Dependencies
- Requires an API key credential to authenticate requests to the external service managing the integration hooks.
- The node uses a base URL configured in the credentials to send HTTP requests.
- The node depends on the external API supporting integration hook updates via a RESTful endpoint accepting JSON payloads.
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: Missing or invalid API credentials will result in authorization failures. Confirm that the API key or token is correctly set up in the node credentials.
- API Endpoint Issues: Network problems or changes in the external API might cause request failures. Check connectivity and API documentation for any updates.
Links and References
- Refer to the external service’s API documentation for detailed information on integration hooks and their settings.
- JSON formatting tools can help validate the
Settingsinput before use.