Actions40
- Account Actions
- Contact Actions
- Meter Actions
- Opportunity Actions
- Other Actions
- Purchase Line Item Actions
- Revenue Line Item Actions
- Website Registration Actions
Overview
This node enables interaction with the SugarCRM API, allowing users to perform various operations on different SugarCRM resources. Specifically for the "Other" resource with the "Delete" operation, it allows deleting a record from a custom SugarCRM module by specifying a custom endpoint and the record ID.
Common scenarios include automating data cleanup or removal of obsolete records in custom modules within SugarCRM. For example, if you have a custom module managing special customer requests, this node can delete specific request records automatically based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| Custom Endpoint | The API endpoint name of the custom SugarCRM module where the record resides (e.g., CustomModule_c). This is required to specify which custom module to target when using the "Other" resource. |
| ID | The unique identifier of the record to delete in the specified custom endpoint. |
Output
The output is a JSON object representing the response from the SugarCRM API after attempting to delete the record. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data is output by this node.
Dependencies
- Requires an active connection to SugarCRM via an API key credential configured in n8n.
- The node uses OAuth2 password grant flow internally to obtain access tokens for authenticating API requests.
- The SugarCRM instance URL and credentials (client ID, client secret, username, password) must be configured in the node's credential settings.
Troubleshooting
Common issues:
- Incorrect or missing custom endpoint name will cause the API call to fail.
- Providing an invalid or non-existent record ID will result in an error indicating the record was not found.
- Authentication failures due to incorrect credentials or expired tokens will prevent the operation from succeeding.
Error messages:
"No records found or unexpected API response structure": This may occur if the record ID does not exist or the API response is malformed.- API authentication errors typically indicate misconfigured credentials; verify all credential fields are correct.
- Network or connectivity errors suggest issues reaching the SugarCRM server; check network access and base URL configuration.
To resolve errors, ensure the custom endpoint and record ID are correct, credentials are valid, and the SugarCRM instance is accessible.