ProspectPro Trigger icon

ProspectPro Trigger

Triggers when new prospects are found or existing ones are updated in ProspectPro.
Join our community

Overview

This node triggers workflows in n8n when new prospects are added or existing prospects are updated in the ProspectPro system. It is designed to poll the ProspectPro API periodically and emit data about prospects that match specified filters such as qualification status, tags, audiences, and owner.

Common scenarios where this node is beneficial include:

  • Automatically processing or enriching prospect data as soon as it changes.
  • Syncing prospect updates with other systems like CRMs or marketing platforms.
  • Triggering notifications or follow-up actions based on prospect qualification or tagging.

For example, you could use this node to trigger a workflow whenever a prospect becomes qualified, then send a notification email to the sales team.

Properties

Name Meaning
Trigger On Event that triggers the node; currently only "Prospect Added or Updated" is supported.
Qualification Status Filter prospects by their qualification status. Options: All, Qualified, Disqualified, Not Qualified.
Tag Names or IDs Filter prospects by one or more tags. You can select from a list or specify tag IDs via expressions.
Audience Names or IDs Filter prospects by one or more audiences (lists). Select 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 using expressions.

Output

The node outputs an array of JSON objects representing prospects that have been added or updated since the last poll. Each object contains the prospect's data as returned by the ProspectPro API, including fields such as changed_time which indicates when the prospect was last modified.

If no new or updated prospects are found, the node returns no output.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the ProspectPro API.
  • Uses internal helper functions to load options dynamically for tags, audiences, and owners.
  • The node polls the ProspectPro API endpoint /prospects to retrieve prospect data.

Troubleshooting

  • No data returned: Ensure that the filters (qualification status, tags, audiences, owner) are set correctly and that there are prospects matching those criteria.
  • API request failures: Check that the API key credential is valid and has sufficient permissions. Network issues or incorrect API URLs can also cause errors.
  • Unexpected response structure warning: This indicates the API returned data in an unexpected format. Verify the API version and consult ProspectPro documentation.
  • Manual mode errors: When running manually, errors during API requests will be thrown immediately. Review error messages for details.

Links and References

Discussion