Overview
This node integrates with SugarCRM to perform various operations on CRM modules such as Accounts, Contacts, Opportunities, Meetings, Leads, and custom complaint modules. Specifically, the 'Delete' operation allows users to delete a record by specifying its module and record ID. This is useful for automating the removal of outdated or incorrect records from SugarCRM. For example, a user can delete a lead or contact record directly from an n8n workflow by providing the module name and the record ID.
Use Case Examples
- Deleting a lead record by specifying the 'Leads' module and the lead's ID.
- Removing a customer complaint record from the 'osy_reclami_da_cliente' module by providing the record ID.
Properties
| Name | Meaning |
|---|---|
| Module | The SugarCRM module from which the record will be deleted. Options include standard modules like Accounts, Contacts, Leads, and custom modules like customer or supplier complaints. |
| Custom endpoint | If 'Other (custom endpoint)' is selected as the module, this property allows specifying the custom module endpoint name. |
| ID | The unique identifier of the record to delete in the specified module. |
Output
JSON
id- The ID of the deleted record.status- The status or result of the delete operation returned by SugarCRM API.
Dependencies
- SugarCRM API with OAuth2 authentication
Troubleshooting
- Ensure the provided record ID exists in the specified module; otherwise, the delete operation will fail.
- Verify that the API credentials have sufficient permissions to delete records in the targeted module.
- If using a custom endpoint, ensure the endpoint name is correct and accessible via the SugarCRM API.
- Common errors include authentication failures, invalid record IDs, or insufficient permissions. Check the error message for details and verify credentials and input parameters.
Links
- SugarCRM REST API Documentation - Official documentation for SugarCRM REST API endpoints and operations.