Actions11
Overview
This node integrates with the ProspectPro API to create an event associated with a specific prospect. It allows users to log various types of interactions or notes related to a prospect, such as phone calls, emails, meetings, or general notes. This functionality is useful for sales, marketing, or customer success teams who want to keep track of their engagement history with prospects directly within their workflow automation.
Practical examples:
- Automatically logging a phone call event after a call is completed.
- Creating a note event when a new piece of information about a prospect is gathered.
- Recording an email sent to a prospect as an event for future reference.
Properties
| Name | Meaning |
|---|---|
| Prospect ID | The unique identifier of the prospect for whom the event is being created. |
| Event Type | The type of event to create. Options include: Phone Call, Email, Meeting, and Note. |
| Content | The textual content or message describing the event details. |
Output
The node outputs JSON data representing the newly created event object as returned by the ProspectPro API. This typically includes details such as the event ID, associated prospect ID, event type, content/message, timestamps, and any other metadata provided by the API.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the ProspectPro API.
- The base URL used for requests is
https://api.prospectpro.nl/v1.2. - The node uses HTTP POST requests to the
/eventsendpoint to create events. - No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Missing or invalid Prospect ID: The node requires a valid prospect ID to associate the event. Ensure the ID is correct and corresponds to an existing prospect in ProspectPro.
- Invalid event type: Only the predefined event types (Phone Call, Email, Meeting, Note) are accepted. Using unsupported values will cause errors.
- Empty content: The event content/message is mandatory. Providing an empty string may result in rejection by the API.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API rate limits or downtime: If the API returns errors related to rate limiting or service availability, retry later or check ProspectPro status.
Links and References
- ProspectPro API Documentation (hypothetical link for reference)
- n8n documentation on creating custom nodes