Perfex CRM

Consumir API do Perfex CRM

Actions5

Lead Actions

Overview

This node integrates with the Perfex CRM API to manage leads. Specifically, the "Atualizar" (Update) operation allows users to update existing lead records in their CRM system by specifying the lead ID and providing updated field values.

Common scenarios for this node include:

Keeping lead information up-to-date after receiving new data from other systems or manual inputs.
Automating lead status changes or reassignments based on workflow triggers.
Enriching lead profiles with additional optional details such as contact info, tags, or custom dates.

For example, a sales automation workflow could use this node to update a lead’s status and assigned salesperson after a qualification step completes.

Properties

Name	Meaning
ID do Lead	The unique identifier of the lead to update.
Campos Obrigatórios	Required fields for the lead update:
	- Fonte: Source of the lead (required).
	- Status: Current status of the lead (required).
	- Nome: Name of the lead (required).
	- Responsável: ID of the person responsible for the lead (required).
Campos Opcionais	Optional fields that can be updated for the lead, including:
	- ID do Cliente: Related client ID.
	- Tags: Tags associated with the lead.
	- Contato: Contact person for the lead.
	- Cargo: Job title or position of the lead.
	- Email: Email address of the lead.
	- Website: Lead's website URL.
	- Telefone: Phone number.
	- Empresa: Company name.
	- Endereço: Address.
	- Cidade: City.
	- CEP: Postal code.
	- Estado: State.
	- País: Country.
	- Idioma Padrão: Default language.
	- Descrição: Description of the lead.
	- Data de Contato Personalizada: Custom contact date.
	- Contatado Hoje: Whether the lead was contacted today.
	- É Público: Whether the lead is public.
	- Último Contato: Date of last contact with the lead.

Output

The node outputs JSON data representing the response from the Perfex CRM API after updating the lead. This typically includes the updated lead object with all its fields as stored in the CRM.

The output structure is:

{
  "json": {
    // Updated lead data returned by the API
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is produced by this node.

Dependencies

Requires an active connection to the Perfex CRM API.
Needs an API authentication token credential configured in n8n to authorize requests.
Uses HTTP methods (PUT) to send updates to the /api/leads/{leadId} endpoint of the CRM.
Requires the base URL of the Perfex CRM instance and an API key credential.

Troubleshooting

Common issues:
- Invalid or missing lead ID will cause the update to fail.
- Missing required fields (source, status, name, assigned) will result in API errors.
- Incorrect API credentials or URL configuration will cause authentication failures.
- Network connectivity problems may prevent reaching the CRM API.
Error messages:
- Errors returned from the API are passed through; typical messages might indicate invalid input or unauthorized access.
- If the node is set to continue on failure, error details will appear in the output JSON under an error property.
Resolutions:
- Verify the lead ID exists in the CRM before attempting update.
- Ensure all required fields are provided and correctly formatted.
- Confirm API credentials and base URL are correct and have sufficient permissions.
- Check network connectivity and firewall settings.

Links and References

Perfex CRM API Documentation (general reference for API endpoints)
n8n Documentation - Creating Custom Nodes

Perfex CRMInstall