Perfex CRMInstall

Overview

This node integrates with the Perfex CRM system via the WON API, allowing users to perform various operations on different resources such as clients, contacts, leads, projects, tasks, and invoices. Specifically for the Lead resource and the Obter (get) operation, the node retrieves detailed information about a specific lead by its ID.

Common scenarios where this node is beneficial include:

• Fetching lead details to enrich workflows with up-to-date customer prospect data.
• Automating follow-up processes based on lead information.
• Integrating lead data into other systems or reports.

For example, you can use this node to get a lead's contact info, status, and company details by providing the lead's unique ID, then use that data downstream in your automation.

Properties

Output

The node outputs a JSON object containing the full details of the requested lead as returned by the Perfex CRM WON API. The structure includes fields such as name, source, status, assigned user, email, phone number, company, address, city, state, country, zip code, and description.

Example output JSON (simplified):

{
  "id": "123",
  "name": "Lead Name",
  "source": 1,
  "status": 2,
  "assigned": 5,
  "email": "lead@example.com",
  "phonenumber": "+5511999999999",
  "company": "Company Ltda",
  "address": "Rua Exemplo, 100",
  "city": "São Paulo",
  "state": "SP",
  "country": "Brasil",
  "zip": "01000-000",
  "description": "Lead description here"
}

The node does not output binary data.

Dependencies

• Requires an API token credential for authenticating with the Perfex CRM WON API.
• Uses Axios HTTP client internally to make REST API calls.
• The base URL and API token must be configured in the node credentials.
• The node expects the API to respond with JSON data.

Troubleshooting

• Authentication errors: If the API token is invalid or missing, the node will throw an authentication error. Ensure the API token credential is correctly set.
• Resource not found: If the provided lead ID does not exist, a "Resource not found" error will be thrown.
• Invalid input: The node validates some fields like email format when creating or updating leads; invalid emails cause errors.
• Connection issues: Network problems or incorrect base URL configuration may cause connection errors.
• JSON parsing errors: When using filters or options, ensure JSON strings are valid to avoid parsing errors.

To resolve errors:

• Double-check the lead ID is correct and exists in the CRM.
• Verify API token and base URL credentials.
• Validate any JSON inputs used in filters or options.
• Check network connectivity to the API endpoint.

Links and References

• Perfex CRM Official Website
• Axios HTTP Client Documentation
• n8n Documentation - Creating Custom Nodes