Actions30
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 Contato (Contact) resource with the Obter (Get) operation, the node retrieves detailed information about a specific contact by its ID.
Common scenarios where this node is beneficial include:
- Fetching contact details to enrich workflows with up-to-date customer information.
- Automating CRM data retrieval for reporting or synchronization with other systems.
- Integrating contact data into marketing, sales, or support automation pipelines.
Practical example:
You want to retrieve the full details of a contact in your CRM by providing their unique contact ID, then use that data to send personalized emails or update records in another system.
Properties
| Name | Meaning |
|---|---|
| ID do Contato | The unique identifier of the contact to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the contact's details as returned by the Perfex CRM API. The structure depends on the API response but typically includes fields such as contact name, email, phone number, associated client ID, job title, status flags (e.g., active, primary), and other contact-specific information.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"id": "123",
"userid": "456",
"firstname": "John",
"lastname": "Doe",
"email": "john.doe@example.com",
"phonenumber": "+5511999999999",
"title": "Manager",
"is_primary": true,
"active": true
}
Dependencies
- Requires an API token credential for authenticating requests to the Perfex CRM WON API.
- The node uses Axios HTTP client internally to communicate with the API endpoint.
- The base URL and API token must be configured in the node credentials before execution.
Troubleshooting
Common Issues
- Invalid Contact ID: If the provided contact ID does not exist, the node will throw a "Resource not found" error.
- Authentication Errors: Missing or invalid API token will result in authentication errors.
- Connection Problems: Network issues or incorrect API URL configuration can cause connection failures.
- Malformed Input: Providing empty or invalid contact ID will cause the node to fail.
Error Messages and Resolutions
| Error Message | Cause | Resolution |
|---|---|---|
| "Erro de autenticação: Token inválido ou não fornecido" | Invalid or missing API token | Verify and provide a valid API token credential. |
| "Recurso não encontrado" | Contact ID does not exist | Check the contact ID for correctness. |
| "Erro de conexão com o servidor" | Network or server unreachable | Ensure network connectivity and correct API URL. |
| "Erro: |
Other unexpected errors | Review the error message and adjust inputs/config. |
Links and References
- Perfex CRM Official Website
- WON API Documentation (if available) (Replace with actual link if known)
- Axios HTTP Client
Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior may depend on external API responses and configurations.