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 integrates with the SugarCRM API to perform various operations on CRM resources such as Accounts, Contacts, Opportunities, and others. Specifically for the Account - Delete operation, it deletes an existing Account record in SugarCRM by its unique ID.
Common scenarios where this node is useful include:
- Automating cleanup of outdated or incorrect account records.
- Integrating with other systems to remove accounts when they are deleted elsewhere.
- Managing CRM data lifecycle programmatically within workflows.
Example: Automatically delete an Account record in SugarCRM when a related customer is removed from another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account record to delete. This is required to specify which record should be removed. |
Output
The output JSON contains the response from the SugarCRM API after attempting to delete the specified Account 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 (an API authentication token).
- The node uses OAuth2 password grant flow internally to obtain access tokens.
- The SugarCRM instance URL and credentials (client ID, client secret, username, password) must be configured in n8n credentials for this node to function.
Troubleshooting
Common issues:
- Invalid or missing Account ID: The node requires a valid record ID to delete; ensure the ID is correct.
- Authentication failures: Check that the SugarCRM credentials are correctly set up and have sufficient permissions.
- Network or API endpoint errors: Verify the SugarCRM base URL and network connectivity.
Error messages:
"No records found or unexpected API response structure": May occur if the record ID does not exist or the API response is malformed.- Authentication errors typically indicate invalid credentials or expired tokens.
To resolve errors, verify input parameters, credentials, and network access.