Overview
This node acts as a trigger for Visualping job events. It listens for changes or updates related to a specific Visualping monitoring job and triggers the workflow whenever such an event occurs. This is useful for automating workflows based on webpage change detection without manual polling.
Common scenarios include:
- Automatically processing or notifying when a monitored webpage changes.
- Integrating Visualping alerts with other systems like Slack, email, or databases.
- Triggering data extraction or further analysis workflows upon webpage updates.
For example, you can set up this trigger to watch a product page for price changes and automatically update your inventory system or notify your sales team.
Properties
| Name | Meaning |
|---|---|
| Job | Select a Visualping monitoring job either from a searchable list of existing jobs or by entering a valid job ID manually. The job represents the webpage being monitored for changes. |
| New to Visualping? Create your account here and explore our n8n help guide to get started. | Informational notice with links to create a Visualping account and access documentation. |
The "Job" property supports two modes:
- From List: Search and select from existing Visualping jobs.
- ID: Enter a numeric job ID directly (must be at least two digits).
Output
The node outputs JSON data representing the webhook payload received from Visualping when a job event occurs. The output structure includes all details sent by Visualping about the job event in the json field.
Example output JSON structure (simplified):
{
"jobId": 123456,
"url": "https://example.com",
"changeDetected": true,
"timestamp": "2024-06-01T12:00:00Z",
...
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Visualping to authenticate API requests.
- Needs a publicly accessible webhook URL configured in n8n to receive Visualping job event notifications.
- The node uses Visualping's API to manage webhook registration and verify webhook existence.
Troubleshooting
- Webhook not triggering: Ensure that the webhook URL is correctly registered with Visualping for the selected job. Use the node’s built-in webhook management methods to check and create the webhook.
- Invalid Job ID error: When entering a job ID manually, it must be numeric and at least two digits. Otherwise, the node will reject it.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- 404 errors during webhook checks: This usually means the webhook is not registered yet; try creating it again via the node.
- Network issues: The node requires that n8n instance is reachable from Visualping servers to receive webhook calls.