ProspectPro icon

ProspectPro

Get data from the ProspectPro API.

Actions11

Overview

This node integrates with the ProspectPro API to manage "Event" resources, specifically allowing users to delete an event by its ID. The delete operation permanently removes the specified event from the ProspectPro system.

Common scenarios for this node include cleaning up outdated or incorrect events, managing event lifecycle in marketing automation workflows, or removing test data after validation.

For example, a user might automate the deletion of events that are no longer relevant or were created erroneously during testing, ensuring their ProspectPro data remains accurate and up-to-date.

Properties

Name Meaning
Event ID The unique identifier of the event to delete. This is required. WARNING: This action cannot be undone.

Output

The node outputs JSON data representing the response from the ProspectPro API after attempting to delete the event. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the ProspectPro API.
  • Requires an API authentication token (configured as credentials in n8n).
  • The base URL used for requests is https://api.prospectpro.nl/v1.2.
  • The node uses HTTP DELETE method on the /events endpoint with the event ID passed as a query string parameter.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent Event ID will result in an error from the API.
    • Missing or invalid API credentials will cause authentication failures.
    • Network connectivity issues can prevent the request from reaching the API.
  • Error Messages:

    • "Event not found" — Verify the Event ID is correct and exists.
    • "Unauthorized" or "Authentication failed" — Check that the API key credential is valid and properly configured.
    • "Request failed" or timeout errors — Ensure network connectivity and that the ProspectPro API service is operational.

To resolve these, double-check the Event ID input, verify API credentials, and ensure stable internet access.

Links and References

Discussion