Overview
This node acts as a trigger for ProspectPro, a platform managing prospects data. It activates when new prospects are found or existing ones are updated in ProspectPro. The node periodically polls the ProspectPro API to detect changes based on specified filters such as qualification status, tags, audiences, and owner.
Common scenarios where this node is beneficial include:
- Automatically initiating workflows when new qualified leads appear.
- Monitoring updates to prospect information to keep CRM systems synchronized.
- Filtering prospects by specific tags or owners to trigger targeted marketing campaigns.
For example, you could use this node to trigger an email campaign whenever a prospect becomes qualified or to update a database record when a prospect's details change.
Properties
| Name | Meaning |
|---|---|
| Qualification Status | Filter prospects by their qualification status. Options: All, Qualified, Disqualified, Not Qualified |
| Tag Names or IDs | Filter prospects by tags. Choose from a list or specify tag IDs via expressions. |
| Audience Names or IDs | Filter prospects by audiences (mapped to "lists" parameter). Choose from a list or specify IDs via expressions. |
| Owner Name or ID | Filter prospects by owner. Choose from a list or specify an owner ID via expressions. |
Output
The node outputs an array of JSON objects representing the prospects that match the filter criteria and have been created or updated since the last poll. Each object contains prospect data fields as returned by the ProspectPro API, including but not limited to identifiers, qualification status, tags, audiences, owner, and timestamps like changed_time.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the ProspectPro API.
- Uses internal methods to load options dynamically for tags, audiences, and owners.
- The node depends on network connectivity to ProspectPro’s REST API endpoint
/prospects. - No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Empty or Unexpected Response: If the API returns an unexpected structure, the node logs a warning and returns no data. Verify that the API credentials are correct and that the ProspectPro API is operational.
- API Request Failures: Errors during API requests are logged. In manual mode or on first run, errors will be thrown to alert the user. Check network connectivity and API key validity.
- No Data Returned: If no prospects match the filters or no changes occurred since the last poll, the node returns no output. Adjust filters or verify that prospects exist matching the criteria.
- Rate Limits or Timeouts: Frequent polling may hit API rate limits. Adjust polling intervals accordingly.
Links and References
- n8n Expressions Documentation
- ProspectPro API documentation (not provided here; consult your ProspectPro account resources)