Actions40
- Job Actions
- Account Hierarchy Actions
- Cryptography Actions
- Customer Hierarchy Actions
- File Explorer Actions
- Generic API Actions
- Invoice Actions
- Mediation Actions
- Order Actions
- Quote Actions
- Subscription Actions
Overview
The Opencell - Create Quote node allows you to create a new quote in the Opencell CPQ (Configure, Price, Quote) system via its API. This is useful for automating sales processes, integrating quoting into customer workflows, or synchronizing quote data between systems. For example, you might use this node to automatically generate quotes when a new opportunity is created in your CRM, or to trigger quote creation as part of an order management workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects the authentication method: Basic Authentication or OAuth2. |
| Quote Code | string | Unique identifier for the quote. Required. |
| Applicant Account Code | string | The billing account code of the applicant. Required. |
| Quote Version | collection | Details about the version of the quote, including current version, contract code, dates, etc. |
| Current Version | number | The version number of the quote. |
| Quote Code | string | The code associated with the quote version. |
| Contract Code | string | Contract code related to the quote version. |
| Short Description | string | Short description for the quote version. |
| Status Date | dateTime | Status date for the quote version. |
| Start Date | dateTime | Start date for the quote version. |
| End Date | dateTime | End date for the quote version. |
| Additional Fields | collection | Optional extra fields for the quote. |
| Billable Account Code | string | The billable account code for the quote. |
| Description | string | Description of the quote. |
| Quote Date | dateTime | The date of the quote. |
| Seller Code | string | Seller's code associated with the quote. |
| Status | options | Status of the quote (Accepted, Approved, Cancelled, In Progress, Pending, Rejected). |
| Body Content Type | hidden | Always set to "multipart-form-data" (used internally for request formatting). |
Output
- The node returns the response from the Opencell API after creating the quote.
- The output is provided in the
jsonfield and will contain the details of the newly created quote as returned by Opencell. - The exact structure of the output depends on the Opencell API, but typically includes identifiers, status, and any data submitted or generated by the API.
Example output structure:
{
"json": {
// ...fields returned by Opencell, e.g.:
"code": "Q12345",
"applicantAccountCode": "ACC001",
"status": "IN_PROGRESS",
"quoteVersion": {
"currentVersion": 1,
"contractCode": "C001",
"startDate": "2025-01-01T00:00:00Z",
"endDate": "2025-12-31T23:59:59Z"
},
// other fields...
}
}
Dependencies
- External Service: Requires access to an Opencell instance with the CPQ module enabled.
- Authentication: You must configure either Basic Authentication or OAuth2 credentials in n8n for the Opencell API.
- n8n Configuration: Credentials must be set up in the n8n credential manager under the names
opencellApi(for Basic Auth) oropencellOAuth2Api(for OAuth2).
Troubleshooting
- Missing Required Fields: If required fields like "Quote Code" or "Applicant Account Code" are missing, the node will throw an error. Ensure all mandatory properties are filled.
- Authentication Errors: If credentials are incorrect or missing, you may see errors such as "Username/password error" or "Invalid credentials." Double-check your credential setup.
- API Connectivity Issues: Network problems or incorrect Opencell API URLs can result in connection errors. Verify that your n8n instance can reach the Opencell server.
- Field Format Errors: Dates and other structured fields must be in the correct format expected by Opencell. Invalid formats may cause API errors.
Links and References
Tip: Always test your configuration with sample data before deploying in production to ensure all required fields and authentication are set correctly.