PerfexCRM icon

PerfexCRM

Interact with PerfexCRM API

Actions11

Overview

This node integrates with the PerfexCRM API to manage customer data. Specifically, the "Customer - Get" operation retrieves detailed information about a single customer by their unique ID. This is useful in scenarios where you need to fetch up-to-date customer details for use in workflows such as CRM automation, reporting, or syncing customer data with other systems.

For example, you might use this node to:

  • Retrieve a customer's profile before sending a personalized email.
  • Fetch customer details to update records in another database.
  • Access customer information to trigger conditional workflow steps based on customer attributes.

Properties

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

Output

The output is a JSON object representing the customer data returned from the PerfexCRM API. It contains all available fields for the specified customer, such as name, contact details, company info, and any other metadata stored in the CRM.

The node does not output binary data; it only returns structured JSON data corresponding to the customer record.

Example output structure (simplified):

{
  "id": "123",
  "company": "Example Company",
  "email": "customer@example.com",
  "phonenumber": "1234567890",
  "address": "123 Example St",
  ...
}

Dependencies

  • Requires an active connection to the PerfexCRM API via an API key credential configured in n8n.
  • The node uses the base URL and API version from the provided credentials to construct requests.
  • Internet access to the PerfexCRM instance is necessary.

Troubleshooting

  • Invalid Customer ID: If the provided Customer ID does not exist, the API will likely return a 404 error. Verify the ID is correct.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the PerfexCRM server will cause request failures.
  • API Version Mismatch: Using an incorrect API version in credentials may lead to unexpected errors.

If the node throws an error, check the error message for details. Enabling "Continue On Fail" allows the workflow to proceed even if some executions fail, returning error details in the output JSON.

Links and References

Discussion