Overview
This node integrates with the Corbee CRM API to manage customer attendances (service interactions or cases). The "Listar Atendimentos" (List Attendances) operation retrieves a list of attendances filtered by optional criteria such as document number (CPF), phone, pagination page, and limit on the number of results.
Typical use cases include:
- Fetching recent or specific attendances for reporting or analysis.
- Integrating attendance data into workflows for follow-up actions.
- Filtering attendances by customer identifiers like CPF or phone number.
For example, you could use this node to get all attendances related to a particular customer's CPF or to paginate through attendances in batches of 50.
Properties
| Name | Meaning |
|---|---|
| Opções Adicionais | Additional options including: • Continue On Fail (boolean) • Custom Headers (JSON) • Query Parameters (JSON) • Timeout (number, milliseconds) |
| Filtros | Filters to narrow down the attendances list: • Documento (CPF) (string) • Limite (limit, number) • Página (page number, number) • Telefone (phone, string) |
Output
The output is an array of JSON objects representing attendances retrieved from the Corbee CRM API. Each item corresponds to one attendance record with its full details as returned by the API.
If multiple attendances are returned, each is output as a separate item paired with the input item index.
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 the CorbeeHelpers utility class internally to make HTTP requests to the API endpoints.
- Network connectivity to the Corbee CRM API endpoint is necessary.
- Optional custom headers, query parameters, and timeout can be configured via additional options.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect filter values (e.g., invalid CPF format) may result in empty responses or API errors.
- Network timeouts if the API is unreachable or slow; can be adjusted with the timeout option.
Error handling:
- If "Continue On Fail" is enabled, errors return as JSON objects with
erroranddetailsfields instead of stopping execution. - Without "Continue On Fail", errors throw exceptions that halt the workflow.
- If "Continue On Fail" is enabled, errors return as JSON objects with
How to resolve:
- Verify API credentials and permissions.
- Check filter inputs for correctness.
- Adjust timeout settings if needed.
- Enable "Continue On Fail" to handle intermittent API issues gracefully.