Actions10
Overview
This node integrates with the Corbee CRM API to manage customer attendances and related data. Specifically, the "Marcar Perdido" (Mark Lost) operation marks a given attendance record as lost, associating it with a reason for loss.
Common scenarios where this node is beneficial include:
- Sales or service workflows where an attendance (customer interaction or case) needs to be marked as lost due to various reasons.
- Automating CRM updates when a deal or service request is no longer progressing.
- Tracking reasons for lost opportunities to improve business processes.
Practical example:
- A sales automation workflow detects that a lead did not convert and uses this node to mark the corresponding attendance as lost, specifying the reason ID for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| ID Do Atendimento | The unique identifier of the attendance record to mark 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 of the updated attendance status and any relevant metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Corbee CRM API.
- The node depends on the CorbeeHelpers class internally to handle API requests.
- Network access to the Corbee CRM API endpoint is necessary.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
Common issues:
- Invalid or missing attendance ID will cause the API call to fail.
- Providing an invalid or non-existent reason loss ID may result in an error or unexpected behavior.
- Network connectivity problems can prevent successful API communication.
- Incorrect API credentials will cause authentication failures.
Error messages:
- Errors thrown by the node generally originate from the API response or internal validation.
- If the attendance ID is missing or empty, the node will likely throw an error indicating a required parameter is missing.
- API errors related to authorization or resource not found will be propagated and should be checked in the node execution logs.
Resolution tips:
- Ensure the attendance ID is correct and corresponds to an existing attendance in Corbee CRM.
- Verify the reason loss ID is valid and recognized by the system.
- Confirm API credentials are correctly configured and have sufficient permissions.
- Check network connectivity and firewall settings if API calls fail.