Actions11
Overview
The "Event - Get Many" operation in this node retrieves multiple event records associated with a specific prospect from the ProspectPro API. This is useful when you want to analyze or process all events linked to a particular prospect, such as tracking user interactions, monitoring engagement, or auditing activity history.
Practical examples include:
- Fetching all website visit events for a prospect to understand their browsing behavior.
- Retrieving all conversion or purchase events tied to a prospect for sales analysis.
- Gathering event data to trigger follow-up workflows based on prospect activity.
Properties
| Name | Meaning |
|---|---|
| Prospect ID | The unique identifier of the prospect whose events you want to retrieve. This is a required string. |
| Detailed Output | A boolean flag indicating whether to return detailed output including metadata like total number of events. If true, the response returns a single item with details instead of an array of events. |
Output
The node outputs JSON data representing the events retrieved for the specified prospect. Typically, this will be an array of event objects, each containing information about individual events (such as event type, timestamp, and related metadata).
If the "Detailed Output" property is enabled, the output changes to a single JSON object that includes summary details like the total count of events found, rather than an array of event items.
The node does not output binary data.
Dependencies
- Requires an active connection to the ProspectPro API via an API key credential configured in n8n.
- The base URL used for requests is
https://api.prospectpro.nl/v1.2. - Proper permissions on the API key are necessary to read event data for prospects.
Troubleshooting
- Missing or invalid Prospect ID: Since the Prospect ID is required, omitting it or providing an incorrect ID will result in errors or empty responses. Ensure the ID is correct and corresponds to an existing prospect.
- API authentication errors: If the API key credential is missing, expired, or lacks proper permissions, the node will fail to authenticate. Verify the API key configuration in n8n.
- Empty event list: If no events exist for the given prospect, the node will return an empty array unless "Detailed Output" is enabled, which may return a summary with zero count.
- Unexpected output format: Enabling "Detailed Output" changes the response structure from an array to a single object. Workflows expecting an array should handle this accordingly.
Links and References
- ProspectPro API Documentation (general reference for endpoints and data structures)
- n8n Documentation on Creating Custom Nodes