Perfex

Consume Perfex API
Join our community

Actions14

Overview

This node integrates with the Perfex API to manage "Lead" resources. Specifically, the "Get Lead" operation retrieves detailed information about a single lead by its unique ID. This is useful in scenarios where you want to fetch up-to-date lead data from your CRM system for further processing, reporting, or automation workflows.

Practical examples:

  • Automatically retrieving lead details when a new event occurs in another system.
  • Enriching customer profiles in your database with the latest lead information.
  • Triggering follow-up actions based on specific lead attributes fetched dynamically.

Properties

Name Meaning
Lead ID The unique identifier of the lead to retrieve. This is a required string input.

Output

The output is a JSON object representing the lead's data as returned by the Perfex API. It contains all available fields and properties of the lead resource, such as name, email, company, status, and any custom fields defined in the Perfex system.

If multiple leads were retrieved (not applicable for this single-get operation), the output would be an array of such objects. For the "Get Lead" operation, the output is a single JSON object wrapped inside an array with one item.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Perfex API via an API key credential configured in n8n.
  • The node uses the base URL provided in the credentials to make authenticated HTTP requests.
  • No additional external dependencies are needed beyond the configured API access.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID will cause the API request to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • If the lead ID does not exist, the API may return a 404 error indicating the lead was not found.
    • Authentication failures typically return 401 or 403 errors; verify that the API key and base URL are correct.
    • Rate limiting or server errors from the API will propagate as errors; consider implementing retry logic or checking API usage limits.

  • Resolution tips:

    • Double-check the Lead ID value for correctness.
    • Ensure the API key credential is valid and has necessary permissions.
    • Test connectivity to the Perfex API endpoint outside n8n to isolate network issues.

Links and References

Discussion