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 Contacts, Accounts, Opportunities, and others. Specifically for the Contact - Update operation, it updates an existing contact record in SugarCRM by its ID with new or modified data fields.
Typical use cases include:
- Synchronizing updated contact information from other systems into SugarCRM.
- Automating bulk updates of contact details based on external triggers.
- Modifying specific fields like name or description without manually accessing SugarCRM.
For example, you might update a contact’s phone number or address after receiving new customer data from a form submission.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the contact record to update. |
| Additional Fields | Optional fields to update on the contact, including: |
| - Name: The contact's name. | |
| - Description: A description or notes about the contact. | |
| Custom JSON Payload | A JSON object allowing custom fields or complex data structures to be added to the request body. |
| Send JSON Body | Boolean flag indicating whether to send a JSON body with the request. |
| JSON Body | The raw JSON body to send with the request if "Send JSON Body" is enabled. |
Output
The node outputs the updated contact record as a JSON object in the json output field. This includes all fields returned by the SugarCRM API after the update operation, reflecting the current state of the contact.
If multiple items are processed, the output is an array of such JSON objects, each corresponding to one updated contact.
The node does not output binary data.
Dependencies
- Requires connection to a SugarCRM instance via its REST API (version v11_11).
- Needs an API authentication token obtained through OAuth2 password grant using credentials configured in n8n.
- The node expects valid SugarCRM API credentials with permissions to update contact records.
- Network access to the SugarCRM base URL must be available.
Troubleshooting
- Invalid ID error: If the provided contact ID does not exist or is malformed, the API will return an error. Verify the ID is correct and corresponds to an existing contact.
- Authentication failures: Errors related to invalid or expired tokens indicate issues with the configured API credentials. Recheck credentials and ensure they have proper access rights.
- Malformed JSON: If the "Custom JSON Payload" or "JSON Body" contains invalid JSON, parsing will fail. Validate JSON syntax before input.
- Permission denied: Insufficient permissions in SugarCRM for updating contacts will cause errors. Confirm user roles and API scopes.
- Empty response or no changes: If no fields are specified to update, the API may return the original record unchanged. Ensure at least one field is provided in "Additional Fields" or custom JSON.