ProspectPro icon

ProspectPro

Get data from the ProspectPro API.

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 history, or aggregating event data for reporting.

Practical examples:

  • Fetching all website visit events for a prospect to understand their browsing behavior.
  • Retrieving all purchase or conversion events tied to a prospect for sales analysis.
  • Collecting event logs to trigger follow-up actions or notifications based on prospect activity.

Properties

Name Meaning
Prospect ID The unique identifier of the prospect whose events you want to retrieve.
Detailed Output Whether to return detailed output including metadata like the total number of events found. If enabled, the response returns a single item instead of an array. Values: true or false.

Output

The node outputs JSON data containing the events retrieved for the specified prospect ID.

  • When Detailed Output is disabled (false), the output is an array of event objects representing each event related to the prospect.
  • When Detailed Output is enabled (true), the output contains a single object with additional details such as the total count of events found, rather than an array of individual events.

No binary data output is indicated for this operation.

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.
  • The node sends HTTP GET requests to the /events endpoint with query parameters including the prospect ID and optionally a flag controlling header inclusion.

Troubleshooting

  • Missing or invalid Prospect ID: Since the Prospect ID is required, omitting it or providing an incorrect ID will likely result in an error or empty results. Ensure the ID is correct and provided.
  • API authentication errors: If the API key credential is missing, expired, or invalid, the node will fail to authenticate. Verify that the API key is correctly set up in n8n credentials.
  • Empty event list: If no events are returned, confirm that the prospect has recorded events in ProspectPro.
  • Unexpected output format: Enabling Detailed Output changes the response structure from an array to a single object. Adjust downstream nodes accordingly.
  • Network or API downtime: Connectivity issues or ProspectPro service interruptions can cause request failures. Check network access and API status.

Links and References

Discussion