Overview
This node integrates with the Corbee CRM API to manage attendances (service or sales interactions) within the CRM system. Specifically, the "Marcar Perdido" (Mark Lost) operation allows users to mark an attendance as lost by providing the attendance ID and a reason for the loss.
Common scenarios where this node is beneficial include:
- Automating the update of attendance statuses in Corbee CRM based on external triggers or workflows.
- Marking sales opportunities or service requests as lost directly from n8n without manual intervention.
- Integrating Corbee CRM attendance management into broader automation pipelines, such as syncing with other systems or notifying teams.
Practical example:
- After a sales opportunity is confirmed lost in another system, this node can be used to mark the corresponding attendance as lost in Corbee CRM, including specifying the reason for the loss.
Properties
| Name | Meaning |
|---|---|
| Opções Adicionais | Additional options including: • Continue On Fail (boolean) • Custom Headers (JSON) • Query Parameters (JSON) • Timeout (number, milliseconds) |
| ID do Atendimento | The unique identifier of the attendance to be marked as lost. |
| Reason Loss ID | Numeric ID representing the reason why the attendance was lost. |
Output
The node outputs JSON data representing the response from the Corbee CRM API after marking the attendance as lost. This typically includes confirmation details about the updated attendance status.
If multiple items are processed, the output is an array of JSON objects, each paired with the corresponding input item.
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 HTTP requests to communicate with Corbee CRM endpoints.
- Optional additional headers, query parameters, and timeout settings can be configured per request.
Troubleshooting
Common issues:
- Invalid or missing attendance ID will cause the API request to fail.
- Providing an invalid or non-existent reason loss ID may result in an error from the API.
- Network timeouts or connectivity issues can interrupt the request.
- Incorrect API credentials will lead to authentication errors.
Error handling:
- If "Continue On Fail" is enabled in additional options, the node will not stop execution on errors but instead output an error object with message and details.
- Without "Continue On Fail," errors will throw and halt the workflow execution.
How to resolve:
- Verify that the attendance ID exists and is correct.
- Confirm the reason loss ID is valid according to Corbee CRM's configuration.
- Check API credentials and permissions.
- Adjust timeout settings if network delays are suspected.
- Use custom headers or query parameters only if required by your API setup.