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
- Teams Actions
- Custom Filters Actions
- Webhooks 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 sending data to or receiving data from other applications. 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 filters 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 that the integration expects. |
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 to authenticate 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
Common issues:
- Invalid or missing Account Id or Hook Id will cause the update to fail.
- Malformed JSON in the Settings property can lead to parsing errors.
- Authentication failures if the API key or credentials are incorrect or expired.
- Network connectivity issues preventing communication with the external API.
Error messages and resolutions:
- "Invalid Account Id or Hook Id": Verify that the IDs provided correspond to existing resources.
- "Failed to parse JSON settings": Ensure the Settings field contains valid JSON syntax.
- "Authentication failed": Check that the API key or authentication token is correctly configured and has not expired.
- "Network error": Confirm network connectivity and that the API endpoint is reachable.
Links and References
- Refer to the external service’s API documentation for detailed information on integration hooks and their settings.
- JSON validation tools can help ensure the Settings input is correctly formatted before use.