PerfexCRM icon

PerfexCRM

Interact with PerfexCRM API

Actions11

Overview

This node integrates with the PerfexCRM API to manage customer data. Specifically, the "Customer - Get Many" operation retrieves multiple customer records from the CRM system. It supports fetching either all customers or a limited subset based on user-defined filters and limits.

Common scenarios where this node is useful include:

  • Synchronizing customer lists from PerfexCRM into other systems.
  • Generating reports or dashboards that require bulk customer data.
  • Filtering customers by active status or searching by terms for targeted marketing or outreach.

For example, you could use this node to fetch all active customers whose names contain a specific keyword, then pass that data downstream for email campaigns or analytics.

Properties

Name Meaning
Return All Whether to return all matching customer records (true) or limit the number of results (false).
Limit Maximum number of customer records to return when "Return All" is false. Minimum value is 1.
Filters Collection of filters to narrow down the results:
  Active Filter customers by their active status. Options: "All", "Active", "Inactive".
  Search Search term to filter customers by matching text fields.

Output

The output is an array of JSON objects representing customer records retrieved from PerfexCRM. Each object corresponds to one customer and contains all available customer fields as returned by the API.

If "Return All" is true, the node attempts to fetch up to 1000 customers in one request. Otherwise, it respects the specified "Limit".

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "id": 123,
    "company": "Acme Corp",
    "active": 1,
    "email": "contact@acme.com",
    ...
  },
  {
    "id": 124,
    "company": "Beta LLC",
    "active": 0,
    "email": "info@beta.com",
    ...
  }
]

Dependencies

  • Requires an API key credential configured for accessing the PerfexCRM API.
  • The node uses the base URL and API version from the provided credentials.
  • Network access to the PerfexCRM instance is necessary.

Troubleshooting

  • Empty results: Check if filters are too restrictive or if the search term matches no customers.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • API rate limits or timeouts: If requesting all customers ("Return All" = true), large datasets may cause delays or throttling. Consider using smaller limits.
  • Invalid parameter values: Ensure "Limit" is at least 1 and that filter options are correctly selected.

If the node throws an error related to HTTP requests, inspect the error message for details such as unauthorized access, resource not found, or server errors, and adjust credentials or parameters accordingly.

Links and References

Discussion