Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The "Buscar Perfil Profissional" operation of the "Perfil" (Profile) resource in this custom n8n node allows users to fetch professional profile information for a specified contact from the Evolution API. This is useful in scenarios where you need to retrieve up-to-date professional details about a user or business contact, such as integrating CRM systems, automating contact enrichment, or verifying business profiles before outreach.
Practical Example:
You could use this node in an automation workflow to look up the professional profile of a WhatsApp contact when a new lead is added to your system, enriching your database with additional business information.
Properties
| Display Name | Type | Description |
|---|---|---|
| Nome Da Instância | String | Digite o nome da instância (Enter the instance name). Required. |
| Contato | String | Número do contato (Contact number). Required. |
- Nome Da Instância: The name of the Evolution API instance you want to interact with.
- Contato: The phone number or identifier of the contact whose professional profile you wish to fetch.
Output
The output will be a JSON object (or array of objects) containing the professional profile data retrieved from the Evolution API for the specified contact. The exact structure depends on the API response, but typically includes fields relevant to a professional or business profile.
Note: If the API returns binary data, it will be summarized as such, but for this operation, the output is expected to be JSON.
Dependencies
- External Service: Requires access to the Evolution API.
- API Key/Credentials: You must configure valid Evolution API credentials in n8n under the credential type
evolutionApi. - n8n Configuration: Ensure the node is properly configured with the required properties and credentials.
Troubleshooting
Common Issues:
- Missing or Invalid Credentials: If the Evolution API credentials are not set or are incorrect, authentication errors will occur.
- Unsupported Operation Error: If you select an unsupported resource or operation, the node will throw an error indicating that the function is not supported.
- Invalid Contact Number: Providing an incorrectly formatted or non-existent contact number may result in empty responses or API errors.
Error Messages:
"Operação não suportada."
Meaning: The selected operation is not supported for the chosen resource.
Resolution: Double-check that you have selected the correct resource ("Perfil") and operation ("Buscar Perfil Profissional").- API-specific errors may also be returned in the output if the request fails due to issues like invalid parameters or server problems.
Links and References
If you encounter issues, consult the above documentation or verify your API credentials and input parameters.