Actions10
Overview
The "Alterar Atendimento" operation in the Corbee CRM node allows users to update details of an existing attendance record within the Corbee CRM system. This operation is useful for modifying key attributes of a customer interaction or service case, such as changing its stage in the sales funnel, updating its monetary value, origin, associated organizational unit, tags, or adding additional custom data.
Typical scenarios where this operation is beneficial include:
- Updating the progress of a sales opportunity by moving it to a different funnel stage.
- Adjusting the estimated or actual value of a customer attendance.
- Changing metadata like the source of the attendance or tagging it for categorization.
- Adding or overriding custom JSON data related to the attendance for enhanced tracking or integration purposes.
For example, a sales automation workflow could use this operation to mark an attendance as progressed to a negotiation stage and update its expected revenue value accordingly.
Properties
| Name | Meaning |
|---|---|
| ID Do Atendimento | The unique identifier of the attendance record to be updated (required). |
| Etapa Do Funil (Stage_id) | The ID of the funnel stage to assign to the attendance. |
| Valor (Value) | The monetary value associated with the attendance. |
| Origem (Origin_id) | The ID representing the origin/source of the attendance. |
| Órgão (Organ_id) | The ID of the organizational unit related to the attendance. |
| Tag (Tag_id) | The ID of a tag to apply to the attendance for categorization. |
| Dados Do Atendimento (JSON) | Additional attendance data in JSON format. This data will be merged with the specific fields above; if conflicts occur, the specific fields take priority. |
Output
The output is a JSON object representing the updated attendance record as returned by the Corbee CRM API after the update operation. It contains all relevant fields reflecting the current state of the attendance, including any changes made.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Corbee CRM API.
- The node uses HTTP requests to interact with the Corbee CRM endpoints.
- Proper configuration of the API credentials in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent attendance ID will likely result in an error from the API indicating the resource was not found.
- Incorrectly formatted JSON in the "Dados Do Atendimento (JSON)" field may cause parsing errors.
- Missing required parameters, especially the attendance ID, will prevent the operation from executing.
Error Messages:
- Errors related to authentication usually indicate issues with the API key credential setup.
- Validation errors from the API may occur if numeric fields receive non-numeric input or if IDs do not correspond to existing entities.
Resolutions:
- Verify that the attendance ID exists and is correctly entered.
- Ensure JSON input is valid and well-formed.
- Confirm API credentials are correctly configured and have sufficient permissions.
- Use the Corbee CRM documentation to verify acceptable values for stage, origin, organ, and tag IDs.