Overview
This node is designed to add a webhook URL to the Avito service using a user-provided token. It allows users to register a callback URL (webhook) that Avito can use to send event notifications or messages back to the user’s system. This is useful for automating workflows triggered by Avito events, such as new messages or updates related to listings.
Practical examples include:
- Automatically receiving notifications when a new message arrives on Avito.
- Triggering downstream automation in n8n when specific Avito events occur.
- Integrating Avito messaging with other systems via webhooks.
Properties
| Name | Meaning |
|---|---|
| Avito Webhook | The URL of the webhook endpoint to be registered with Avito to receive event callbacks. |
| User Token | The authentication token used to authorize the request to Avito's API. |
Output
The node outputs a JSON object with a single field:
{
"status": "ok"
}
This indicates that the webhook was successfully added to Avito.
Dependencies
- Requires an API token credential for authenticating with Avito's API.
- Depends on an external module (
AvitoApi) which provides the method to add the webhook. - The node expects the environment to have network access to Avito's API endpoints.
Troubleshooting
- Invalid Token or Authentication Failure: If the provided user token is incorrect or expired, the API call to add the webhook will fail. Ensure the token is valid and has the necessary permissions.
- Incorrect Webhook URL: If the webhook URL is malformed or unreachable, Avito may reject it or fail to deliver events. Verify the URL is correct and publicly accessible.
- Network Issues: Connectivity problems between n8n and Avito's API can cause failures. Check network settings and firewall rules.
- API Errors: If Avito's API returns errors, inspect the error messages for details. Common issues include rate limiting or invalid parameters.
Links and References
- Avito API Documentation (general reference for Avito API usage)
- Webhook Concepts (for understanding webhooks)