Actions10
Overview
This node integrates with the Corbee CRM API to manage customer attendances and related data. Specifically, the "Listar Atendimentos" (List Attendances) operation retrieves a list of customer attendances filtered by various criteria such as CPF (Brazilian individual taxpayer registry identification), stage ID, status, phone number, and attendance ID.
Common scenarios where this node is beneficial include:
- Fetching recent or specific customer attendances for reporting or follow-up.
- Filtering attendances by status or stage in a sales funnel.
- Retrieving attendances linked to a particular customer document or phone number.
Practical example:
- A sales team wants to pull all active attendances for customers with a given CPF to analyze ongoing deals.
- Customer support wants to list attendances filtered by a specific stage to prioritize cases.
Properties
| Name | Meaning |
|---|---|
| Filtros | Collection of filters to narrow down the attendances list. Includes: |
| - CPF | Customer's CPF (will be normalized automatically). |
| - Etapa (Stage ID) | Filter by the stage ID of the attendance. |
| - ID | Filter by attendance ID. |
| - Quantidade Máxima | Maximum number of records to return (0 means no limit). |
| - Status | Filter by attendance status; use "null" to filter attendances with null status. |
| - Telefone | Filter by customer's phone number. |
Output
The output is an array of JSON objects representing attendances matching the specified filters. Each attendance object contains fields returned by the Corbee CRM API, such as:
id: Attendance identifier.customer_cpf: Customer CPF associated with the attendance.customer_phones: Phone numbers linked to the customer.stage_id: Stage ID of the attendance in the sales funnel.status: Status of the attendance.- Other attendance-related details as provided by the API.
If no attendances match the filters, the output JSON will contain a message "SEM ATENDIMENTOS" and an empty data array.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Corbee CRM API.
- The node uses internal helper methods to normalize CPF and handle API requests.
- Network access to the Corbee CRM API endpoint is necessary.
- No additional environment variables are required beyond the API credential.
Troubleshooting
Empty results despite expected data:
Check that the filters are correctly set, especially CPF normalization and phone formatting. Ensure the API credentials have sufficient permissions.Invalid CPF format error:
The node normalizes CPF inputs but expects valid Brazilian CPF formats. Verify the CPF input is correct.API request failures:
Could be due to network issues, invalid credentials, or API downtime. Confirm the API key is valid and the Corbee CRM service is operational.Unsupported operation error:
This occurs if an unsupported operation name is passed. For listing attendances, ensure the operation parameter is exactly"listAttendances".