Actions48
- Account Actions
- Blacklist Actions
- Campaign Actions
- Conversation Actions
- Custom Variable Actions
- Label Actions
- Lead Actions
- Template Actions
- Webhook Actions
Webhook → Edit Webhook
AI-generatedOverview
This node operation allows users to edit an existing webhook in the Aimfox application. It is useful for updating webhook details such as the webhook's name, URL, and the events that trigger the webhook. For example, a user might want to change the URL where webhook payloads are sent or update the events that trigger the webhook to better fit their workflow.
Use Case Examples
- Updating the URL of an existing webhook to a new endpoint.
- Changing the events that trigger the webhook to include additional event types like 'Campaign Created' or 'Message Sent'.
- Renaming a webhook to better reflect its purpose in the automation process.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to edit. |
| Webhook Name | The new name to assign to the webhook. |
| Webhook URL | The new endpoint URL where webhook payloads will be sent. |
| Webhook Events | The list of events that will trigger this webhook. |
Output
JSON
webhookId- The ID of the edited webhook.webhookName- The updated name of the webhook.webhookUrl- The updated URL where webhook payloads will be sent.webhookEvents- The updated list of events that trigger the webhook.
Dependencies
- An API key credential for Aimfox API authentication
Troubleshooting
- Ensure the Webhook ID provided is correct and exists in the Aimfox system to avoid 'webhook not found' errors.
- Verify that the Webhook URL is a valid and reachable endpoint to prevent delivery failures.
- Check that the selected webhook events are valid and supported by the Aimfox API.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option, but be aware of the security implications.
- Timeouts can happen if the server is slow to respond; adjust the timeout setting accordingly.