Overview
This node integrates with the Webmetic service to retrieve data about companies visiting a specified domain. Specifically, the "Returning Visits" resource with the "Get" operation fetches a list of companies that have visited the domain multiple times within a given date range.
Use cases include:
- Marketing teams analyzing repeat visitors to their website to identify engaged prospects.
- Sales teams tracking companies showing ongoing interest by returning to the site.
- Business analysts measuring customer retention or repeated engagement over time.
For example, you could use this node to get all companies that returned to "example.com" in the last 30 days, helping tailor follow-up campaigns or prioritize leads.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain name for which to retrieve company visit data (e.g., "example.com"). |
| Additional Fields | Optional parameters to filter the data by date range: |
| - From Date | Starting date/time or relative date string to specify the beginning of the period (e.g., "2023-01-01", "-30 days", "now"). |
| - To Date | Ending date/time or relative date string to specify the end of the period (e.g., "2023-01-31", "now"). |
Output
The node outputs JSON data containing a list of companies that have returned to the specified domain multiple times within the selected date range. Each item typically includes details about the company and visit metrics as provided by the Webmetic API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Webmetic API.
- The node makes HTTP GET requests to
https://hub.webmetic.de/returning-visits. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Missing or invalid API key credential will cause authentication errors.
- Incorrect domain format or empty domain field may result in no data or API errors.
- Invalid date formats in "From Date" or "To Date" fields can lead to request failures.
Error messages:
- Authentication errors usually indicate problems with the API key; verify and re-enter credentials.
- Validation errors from the API may mention invalid query parameters; check domain and date inputs.
- Network or timeout errors suggest connectivity issues; ensure n8n server can reach the Webmetic API endpoint.
Links and References
- Webmetic API Documentation (for detailed API usage and parameters)
- n8n documentation on HTTP Request Node (conceptual reference for API calls)