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 "Meter" records, specifically supporting the creation of new Meter entries. It allows users to send detailed data about a Meter, including optional fields and custom JSON payloads, to create a record in SugarCRM.
Common scenarios for this node include automating the addition of Meter data collected from external systems or IoT devices into SugarCRM for tracking and analysis. For example, a utility company could use this node to automatically create Meter records when new meters are installed or registered.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra fields to set on the Meter record. Includes: - Name (string): The name of the meter. - Description (string): A description of the meter. |
| Custom JSON Payload | A JSON object that will be merged into the request body, allowing advanced customization beyond predefined fields. |
| Send JSON Body | Boolean flag indicating whether to send a JSON body with the request. If enabled, the JSON Body property becomes available. |
| JSON Body | A raw JSON object to send as the request body. This is used if "Send JSON Body" is enabled, allowing full control over the payload sent to SugarCRM. |
Output
The node outputs an array of JSON objects representing the created Meter records as returned by the SugarCRM API. Each output item corresponds to one input item processed.
The json output field contains the full response data from SugarCRM for the created Meter record, typically including the record's ID and any other fields returned by the API.
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 authenticate requests.
- The node uses OAuth2 password grant flow internally to obtain access tokens based on provided credentials.
- The base URL of the SugarCRM instance and user credentials must be correctly configured in the node's credentials.
Troubleshooting
- Authentication errors: If the node fails due to invalid credentials or inability to obtain an access token, verify that the SugarCRM API credentials (username, password, client ID, client secret, and base URL) are correct and have sufficient permissions.
- Invalid JSON in Custom JSON Payload or JSON Body: Ensure that any JSON entered in these fields is valid and properly formatted; otherwise, parsing errors will occur.
- API errors: Errors returned by SugarCRM (e.g., validation errors on required fields) will be surfaced by the node. Check the error message for details and adjust the input accordingly.
- No records created: If the API returns no data or an unexpected structure, the node may throw an error indicating no records found. Confirm that the request payload meets SugarCRM's requirements.