Actions61
- Contact Actions
- Article Actions
- Voucher Actions
- Invoice Actions
- Down Payment Invoice Actions
- Quotation Actions
- Credit Note Actions
- Delivery Note Actions
- Dunning Actions
- File Actions
- Profile Actions
- Country Actions
- Payment Condition Actions
- Event Subscription Actions
- Recurring Template Actions
- Voucherlist Actions
- Trigger Actions
Overview
This node integrates with the Lexware Office API to manage various business resources, including quotations. Specifically, the "Quotation - Create" operation allows users to create new quotation records in the Lexware system. This is useful for automating sales processes, managing customer offers, and tracking potential orders.
Typical use cases include:
- Automatically generating quotations based on CRM or e-commerce data.
- Creating standardized proposals or estimates for customers.
- Managing quotation lifecycle by setting statuses, priorities, and approval requirements.
For example, a sales automation workflow could generate a quotation when a lead reaches a certain stage, populating details like expected order value, delivery dates, and terms.
Properties
| Name | Meaning |
|---|---|
| Quotation Status | Status of the quotation. Options: All Statuses, Draft, Open, Accepted, Rejected, Expired, Cancelled. |
| Quotation Type | Type of the quotation. Options: All Types, Standard, Proposal, Estimate, Tender, Request. |
| Priority | Priority level of the quotation. Options: All Priorities, Low, Medium, High, Urgent. |
| Probability | Probability percentage (0-100) indicating likelihood of conversion. |
| Expected Order Value | Numeric value representing the expected order amount. |
| Expected Order Date | Expected date for the order (format YYYY-MM-DD). |
| Valid Until | Date until which the quotation is valid (format YYYY-MM-DD). |
| Delivery Date | Expected delivery date (format YYYY-MM-DD). |
| Shipping Date | Expected shipping date (format YYYY-MM-DD). |
| Approval Required | Boolean flag indicating if approval is required for this quotation. |
| Approval Status | Approval status filter. Options: All Statuses, Pending, Approved, Rejected. |
| Reminder Enabled | Boolean flag to enable reminders for the quotation. |
| Reminder Date | Date for sending reminder (format YYYY-MM-DD). |
| Reminder Frequency | Frequency of reminders. Options: Daily, Weekly, Monthly. |
| Customer Reference | Customer reference number as a string. |
| Sales Person | Identifier for the sales person responsible. |
| Sales Channel | Identifier for the sales channel. |
| Campaign | Identifier for the marketing campaign. |
| Lead Source | Identifier for the lead source. |
| Terms and Conditions | Text containing terms and conditions. |
| Terms Version | Version identifier for terms and conditions. |
| Print Layout | ID of the print layout to use for the quotation document. |
| Logo Enabled | Boolean flag indicating whether the company logo should be included. |
| Watermark Enabled | Boolean flag indicating whether a watermark should be applied. |
| XRechnung Enabled | Boolean flag indicating if XRechnung (electronic invoicing standard) is enabled. |
| XRechnung Version | Version of the XRechnung standard to use. |
| XRechnung Profile | Profile identifier for XRechnung. |
| Tags | Comma-separated list of tags associated with the quotation. |
| Notes | Additional notes visible on the quotation. |
| Internal Notes | Internal notes not visible to the customer. |
| External ID | Identifier used in an external system. |
| External System | Name of the external system referencing this quotation. |
| Additional Fields | Collection of extra fields such as name, description, notes, tags, and external ID for the quotation resource. |
Output
The node outputs JSON data representing the created quotation resource as returned by the Lexware Office API. The output includes all relevant fields of the newly created quotation, such as its ID, status, type, dates, values, and any metadata provided during creation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the base URL configured in the credentials to send requests.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields: If required fields for creating a quotation are missing, the node throws an error listing the missing fields. Ensure all mandatory properties are set before execution.
- Authentication Errors: Invalid or missing API key credentials will cause authentication failures. Verify that the API key is correctly configured in the node credentials.
- Invalid Date Formats: Dates must be provided in the correct ISO format (YYYY-MM-DD). Incorrect formats may cause API errors.
- API Rate Limits: Excessive requests might be throttled by the Lexware API. Adjust the workflow frequency or check API rate limit settings.
- Network Issues: Connectivity problems can cause request failures. Confirm network access to the Lexware API endpoint.
Links and References
- Lexware Office API Documentation (official API docs)
- XRechnung Standard Information (for electronic invoicing options)