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 resources. Specifically, for the Revenue Line Item resource and the Update operation, it updates an existing revenue line item record in SugarCRM by its ID. This is useful when you need to modify details of a revenue line item such as its name, description, or any other custom fields.
Common scenarios include:
- Updating sales data or revenue projections linked to opportunities.
- Correcting or enriching revenue line item information after initial creation.
- Automating updates based on external system changes or workflows.
Example: Automatically update the description and name of a revenue line item when a related opportunity stage changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Revenue Line Item record to update. |
| Additional Fields | Optional fields to update on the record. Includes: - Name - Description |
| Custom JSON Payload | A JSON object allowing you to add any additional custom fields or override fields in 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 Revenue Line Item record as JSON. The output structure corresponds to the SugarCRM API response for the updated record, typically including all fields of the revenue line item 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 (version v11_11).
- Needs an API authentication token obtained through OAuth2 password grant using credentials configured in n8n.
- The node depends on proper configuration of these credentials within n8n to authenticate requests.
Troubleshooting
- Invalid ID error: If the provided ID does not exist or is malformed, the API will return an error. Verify the ID is correct and exists in SugarCRM.
- Authentication errors: Ensure that the API credentials (client ID, client secret, username, password) are valid and have sufficient permissions.
- Malformed JSON: When using "Custom JSON Payload" or "JSON Body", ensure the JSON syntax is correct to avoid parsing errors.
- API rate limits or connectivity issues: Network problems or API throttling can cause failures; check network connectivity and API usage limits.
- Unexpected API response structure: If the SugarCRM API changes or returns unexpected data, the node may throw errors. Confirm API version compatibility.