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 Purchase Line Items, specifically supporting the creation of new purchase line item records. It is useful in scenarios where you want to automate adding detailed purchase information into SugarCRM from other systems or workflows, such as syncing e-commerce transactions, inventory purchases, or billing data.
For example, when a new purchase order is processed in an external system, this node can create corresponding purchase line items in SugarCRM automatically, ensuring your CRM reflects up-to-date purchasing details without manual entry.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional fields to add to the purchase line item record. Supported options: Name, Description. |
| Custom JSON Payload | A JSON object allowing you to specify additional custom fields or override default fields in the request body. |
| Send JSON Body | Boolean flag indicating whether to send a custom JSON body with the request. |
| JSON Body | The actual JSON content to send if "Send JSON Body" is enabled. This allows full customization of the request payload. |
Output
The node outputs the created purchase line item record(s) as JSON objects. Each output item corresponds to one created record and contains all fields returned by the SugarCRM API for that record.
The output JSON structure matches the SugarCRM API response for a purchase line item, typically including identifiers, field values, timestamps, and any metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a SugarCRM instance via its REST API.
- Needs an API authentication token (OAuth2 password grant) configured through n8n credentials.
- The node uses the SugarCRM base URL and user credentials (client ID, client secret, username, password) to authenticate and perform requests.
Troubleshooting
- Authentication errors: If the node fails due to invalid credentials or token issues, verify the API credentials are correct and have sufficient permissions.
- Invalid JSON in Custom JSON Payload or JSON Body: Ensure that any JSON entered in these fields is well-formed; otherwise, parsing errors will occur.
- Missing required fields: If the API rejects the creation request, check that mandatory fields for purchase line items are included either via Additional Fields or Custom JSON Payload.
- API endpoint errors: Using an incorrect resource name or custom endpoint may cause 404 or similar errors. Confirm the resource is set to "PurchasedLineItems" and no typos exist.
- Empty response or no records created: This might indicate issues with the request body or API limitations. Review the payload and API documentation.
Links and References
This summary focuses on the "Purchase Line Item" resource and the "Create" operation as requested, based on static analysis of the provided source code and property definitions.