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 SugarCRM records. Specifically, for the Website Registration resource and the Update operation, it updates an existing website registration record in SugarCRM by its ID. This is useful when you need to modify details of a website registration entry, such as updating the name, description, or any custom fields.
Common scenarios include:
- Updating user registration information collected from a website.
- Modifying metadata related to website registrations for marketing or sales tracking.
- Syncing updated registration data from external systems into SugarCRM.
Example: You have a website registration record with ID 12345 and want to update its name and description fields to reflect new information submitted by a user.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Website Registration record to update. |
| Additional Fields | Optional fields to update on the record. Includes: - Name (string) - Description (string) |
| Custom JSON Payload | A JSON object allowing you to specify additional or custom fields beyond the predefined ones. |
| Send JSON Body | Boolean flag indicating whether to send a JSON body with the request. |
| JSON Body | The full JSON body to send with the update request if "Send JSON Body" is enabled. |
Output
The node outputs the updated record's data as JSON. The output structure corresponds to the SugarCRM API response for the updated Website Registration record, typically including all fields of the record after the update.
If multiple items are processed, the output is an array of such JSON objects, each representing one updated record.
No binary data output is produced by this node.
Dependencies
- Requires connection to a SugarCRM instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL and credentials (client ID, client secret, username, password) must be set up properly in the node's credential configuration.
Troubleshooting
Error: No records found or unexpected API response structure
This can occur if the specified ID does not exist or the API returns an unexpected format. Verify the ID is correct and the SugarCRM instance is accessible.Authentication errors
Ensure that the API credentials are valid and have sufficient permissions to update records.JSON parsing errors
When using the "Custom JSON Payload" or "JSON Body" properties, ensure the JSON syntax is correct to avoid parsing failures.Empty or missing ID
The update operation requires a valid record ID. Make sure the "ID" property is provided and not empty.