Perfex CRM

Interagir com o Perfex CRM via WON API

Overview

This node integrates with the Perfex CRM system via the WON API, allowing users to manage various CRM resources such as clients, contacts, leads, projects, tasks, and invoices. Specifically, for the Contato (Contact) resource with the Atualizar (Update) operation, it updates an existing contact's information in the Perfex CRM.

Typical use cases include automating updates to contact details like name, email, phone number, job title, or status within a CRM workflow. For example, when a contact's information changes in another system, this node can synchronize those changes into Perfex CRM automatically.

Properties

Name Meaning
ID do Contato The unique identifier of the contact to update.
Dados do Contato A collection of fields representing the contact data to update. Includes:
- ID do Cliente: ID of the client the contact belongs to
- Nome: Contact's first name
- Sobrenome: Contact's last name
- Email: Contact's email address (must be valid format)
- Telefone: Contact's phone number
- Cargo: Contact's job title
- É Primário: Boolean indicating if this is the primary contact
- Senha: Password for the contact's access to the client portal
- Ativo: Boolean indicating if the contact is active

Output

The node outputs JSON data representing the updated contact record as returned by the Perfex CRM API. This typically includes all the contact's fields after the update.

No binary data output is produced by this node.

Example output JSON structure (simplified):

{
  "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.
  • The base URL and API token must be configured in the node credentials.
  • The API expects JSON payloads and returns JSON responses.

Troubleshooting

  • Invalid Email Error: If the email field is provided but not in a valid email format, the node throws an error "Email inválido". Ensure emails conform to standard formats.
  • Resource Not Found (404): If the contact ID does not exist, the node will throw a "Recurso não encontrado" error.
  • Authentication Errors (401): Occur if the API token is missing or invalid. Verify the API token credential configuration.
  • Validation Errors (422): If the data sent to update the contact is invalid, the node returns detailed validation messages.
  • Connection Issues: Network problems result in "Erro de conexão com o servidor". Check network connectivity and API endpoint availability.
  • Unknown Operation: If an unsupported operation is specified, the node throws "Operação desconhecida".

Links and References


This summary focuses on the "Contato" resource and its "Atualizar" operation as requested.

Discussion