Actions40
- Account Actions
- Contact Actions
- Meter Actions
- Opportunity Actions
- Other Actions
- Purchase Line Item Actions
- Revenue Line Item Actions
- Website Registration Actions
Overview
The node integrates with the SugarCRM API to perform various operations on CRM resources such as Accounts, Contacts, Opportunities, and others. Specifically, for the Account - Update operation, it updates an existing Account record in SugarCRM by sending modified field values to the API.
This node is useful when you want to programmatically update account information stored in SugarCRM from workflows, such as changing account names, descriptions, or other custom fields based on external triggers or data processing.
Example use cases:
- Automatically updating account details after receiving new customer data from a form submission.
- Syncing updated account information from another system into SugarCRM.
- Modifying account records in bulk based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account record to update. |
| Additional Fields | Optional fields to update on the Account, including: - Name (string) - Description (string) |
| Custom JSON Payload | A JSON object allowing additional custom fields or nested data to be included in the update request body. |
| Send JSON Body | Boolean flag indicating whether to send a custom JSON body with the request. If true, the JSON Body property is used. |
| JSON Body | A JSON object representing the full request body to send. Used only if "Send JSON Body" is enabled. |
Output
The output is a JSON array where each item corresponds to the updated Account record returned by the SugarCRM API. Each JSON object contains the updated fields and metadata as returned by the API.
No binary data is output by this node.
Dependencies
- Requires connection to a SugarCRM instance via its REST API.
- Needs an API authentication token obtained through OAuth2 password grant using credentials configured in n8n.
- Requires configuration of an API credential with base URL, client ID, client secret, username, and password for SugarCRM.
Troubleshooting
Common issues:
- Invalid or missing Account ID will cause the update to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Malformed JSON in "Custom JSON Payload" or "JSON Body" properties can cause parsing errors.
- Attempting to update fields not allowed or recognized by SugarCRM may lead to API errors.
Error messages:
"No records found or unexpected API response structure": This indicates that the API did not return expected data, possibly due to invalid parameters or resource identifiers.- Authentication errors typically mention invalid tokens or failed login; verify credentials and permissions.
- JSON parsing errors indicate malformed JSON input; ensure valid JSON syntax.
To resolve these:
- Double-check the Account ID and ensure it exists in SugarCRM.
- Verify API credentials and regenerate tokens if needed.
- Validate JSON inputs using online validators before entering them.
- Consult SugarCRM API documentation for allowed fields and formats.