Actions40
- Associação Actions
- Contato Actions
- Empresa Actions
- Negócio Actions
- Nota Actions
- Produto Actions
- Propriedade Actions
- Segmento Actions
- Tarefa Actions
- Usuário Actions
Overview
This node integrates with the Rvops platform to manage various CRM-related resources, including companies. Specifically, for the "Empresa" (Company) resource and the "Delete a Company" operation, the node allows users to delete a company record by its unique identifier. This is useful in scenarios where companies need to be removed from the CRM system, such as when a client relationship ends or duplicate records are cleaned up.
Practical example:
- Automatically deleting a company from the CRM when it no longer meets business criteria or after a contract termination event triggered elsewhere in your workflow.
Properties
| Name | Meaning |
|---|---|
| Autenticação Do Cliente | Authentication method to use; currently supports "Access Token". |
| ID Da Empresa | The unique identifier of the company to delete. This is required for the delete operation. |
Note: Other properties listed in the full input are related to other operations or resources and are not relevant for the "Delete a Company" operation.
Output
The output JSON contains the response from the API after attempting to delete the company. Typically, this will include confirmation details or status information about the deletion request. The exact structure depends on the API's response but generally includes at least an id field or a success indicator.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential (referred generically as an API authentication token) to authenticate requests to the Rvops API.
- The node uses HTTP methods (DELETE) to interact with the Rvops API endpoints.
- No additional external services beyond the Rvops API are required.
Troubleshooting
Common issues:
- Providing an invalid or non-existent company ID will likely result in an error from the API.
- Missing or incorrect authentication credentials will cause authorization failures.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Errors returned from the API typically include a message and status code. For example:
404 Not Found: The specified company ID does not exist.401 Unauthorized: Authentication failed due to invalid or missing credentials.
- To resolve these errors:
- Verify the company ID is correct and exists in the system.
- Ensure the API authentication token is valid and has necessary permissions.
- Check network connectivity and API endpoint availability.
- Errors returned from the API typically include a message and status code. For example:
Links and References
- Rvops API Documentation (Assumed URL, replace with actual if known)
- n8n documentation on Creating Custom Nodes