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 manage Revenue Line Item records. Specifically, the Create operation allows users to add new Revenue Line Items into their SugarCRM instance. This is useful in scenarios where you want to automate the creation of revenue-related data, such as when processing sales data from an external system or capturing new product revenue details programmatically.
Practical examples include:
- Automatically creating revenue line items when a new opportunity is closed.
- Importing bulk revenue data from spreadsheets or other databases.
- Enriching CRM data by adding detailed revenue information during workflows.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional fields to set on the Revenue Line Item record. Includes: |
| - Name: The name/title of the revenue line item. | |
| - Description: A textual description of the revenue line item. | |
| Custom JSON Payload | A JSON object that will be merged into the request body, allowing custom or additional data. |
| 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 output is a JSON array where each element corresponds to a created Revenue Line Item record returned by the SugarCRM API. Each JSON object contains the properties of the newly created record as returned by the API, typically including identifiers, timestamps, and any fields set during creation.
No binary data is output by this node.
Dependencies
- Requires connection to a SugarCRM instance via its REST API.
- Needs an API authentication token (OAuth2 password grant) configured in n8n credentials for SugarCRM.
- The base URL and credentials (client ID, client secret, username, password) must be properly set up in n8n.
Troubleshooting
- Authentication errors: If the node fails due to invalid credentials or token issues, verify the SugarCRM API credentials and ensure the user has API access.
- Invalid JSON payload: When using "Custom JSON Payload" or "JSON Body," ensure the JSON syntax is correct; otherwise, parsing errors will occur.
- Missing required fields: The API may reject requests missing mandatory fields; ensure at least the minimal required fields for a Revenue Line Item are provided.
- API rate limits or connectivity issues: Network problems or API throttling can cause failures; check network connectivity and SugarCRM API limits.
- Unexpected API response structure: If no records are returned or the response format changes, the node may throw errors about unexpected structure.