.png)
Most manufacturers describe their quoting process as "complicated." What they mean is that it involves too many people, too many systems, and too many manual steps between a customer request and a confirmed order.
The complication is not inherent to the process. It is the result of never having built one.
Quoting is a structured sequence: a request comes in, pricing is retrieved, a document is assembled, it goes to the customer, they accept, an order is created. That sequence is predictable. Predictable sequences can be automated. The manual version exists because no one has mapped it as a workflow yet.
This post walks through a quote-to-order automation in n8n, node by node. Not a conceptual overview - the actual structure, what each node does, and what data moves between them.
Before showing what the automated version looks like, it helps to count the steps of the manual version honestly.
A typical quote request at a mid-market manufacturer plays out like this:
Ten steps. Between steps 5 and 9, the rep has no visibility into whether the customer opened the quote, and the customer has no automated reminder. Between steps 8 and 9, the same data that was on the quote is being entered into the ERP by hand.
The complication is not complexity. It is the accumulation of manual steps where the data is already known and the decisions are already made.
Here is how the same process runs as an n8n automation.
The workflow starts in one of two ways: a web form submission (the customer fills out a structured quote request form on your site), or a CRM deal stage change (a rep marks a deal as "quote requested"). Both paths merge into the same workflow after the trigger.
Using a form trigger is preferable when customers can self-serve the request. Using a CRM trigger preserves the rep's role in initiating the quote while automating everything after that point.
n8n calls the ERP API with the customer ID from the trigger payload. The ERP returns the customer's pricing tier, any active contract discounts, credit status, and open order history. In the same step or a parallel branch, n8n pulls current lead times and inventory status for the requested SKUs.
All of this happens in one or two API calls taking seconds. In the manual process, this is the step where a rep is switching between tabs, checking a spreadsheet, and waiting for someone in operations to reply to a message.
This node applies the logic that governs the final price. The base price is retrieved from the ERP. The customer's tier discount is applied. If the quantity triggers a volume break, the volume discount is applied. If a promotional price is active for the SKU, that takes precedence based on priority rules.
The output is a structured line-item array: SKU, description, quantity, unit price, extended price, lead time. All calculated. No spreadsheet.
n8n populates a quote template with the calculated line items. The template can be a Google Doc, a PDF template managed through a document generation API (DocuPost, Carbone, or similar), or an HTML-to-PDF render. The output is a structured quote document with the customer's name, your company's details, the expiry date, the terms, and the line items.
This is the step that typically takes a rep 20 to 40 minutes in the manual process. In the automated workflow, it takes seconds.
The quote is sent to the customer by email as an attached PDF, with a clear expiry date and a link to accept, decline, or request a revision. Simultaneously, n8n updates the CRM deal record: attaches the quote document, logs the send timestamp, moves the deal to "quote sent," and notes the expiry date.
The sales rep receives a notification that the quote was sent, with a link to the CRM deal. They do not need to remember to follow up; the workflow does it for them.
If the deal has not moved to "accepted" or "declined" within three days, n8n sends a follow-up email to the customer automatically. The message references the original quote by number and invites the customer to reach out with any questions.
If the deal still has not moved by day seven, n8n sends a Slack notification to the sales rep indicating that the quote is approaching expiry and may need a direct call. The follow-up cadence is configurable. The rep is notified at the moment the quote needs human attention, not before and not after.
When the customer accepts (by clicking a link in the quote email, which updates the CRM deal stage, or by the rep manually marking the deal as won), n8n creates the order in the ERP. The line items, quantities, and prices from the approved quote are written directly into the ERP order record. A customer confirmation email is sent with the order number and expected ship date. The fulfillment team receives a notification that a new order has been created.
The rep does not re-enter anything. The same data that was on the quote is now on the order, moved by the workflow, not by hand.
For a clean quote request with standard pricing and no exceptions, the workflow from trigger to quote delivery completes in under a minute. For a request with custom pricing or a product that requires inventory confirmation, the exception path routes that specific question to the right person while processing the rest of the quote automatically.
The sales rep's time shifts from data assembly to the conversations that require judgment: accounts with complex requirements, customers who have questions about specifications, negotiations that need a human in the room.
For the customer, a quote arrives quickly and the follow-up is timely. In a competitive environment where multiple vendors are being evaluated, response speed is part of the evaluation.
Your pricing logic must be documented. If the rules for tier discounts, volume breaks, and promotional pricing exist in a spreadsheet that only two people know how to read, document the logic as explicit IF statements before the build starts. Node 3 can only be as accurate as the rules you provide.
Your ERP API must support quote and order creation. Not all ERP modules have write access enabled by default. Confirm with your IT administrator that the API allows creation of customer records, quote records, and order records before scoping the build.
Your quote template must be structured. If the current Word template is manually formatted differently on every quote, standardize it before automating. The document generation node works from a consistent template. A template with manual overrides applied by hand on each use requires cleanup before it can be automated.
Decide on the trigger. If you use a form trigger, the customer experience changes: they are filling in a structured request rather than sending a freeform email. That is often a better experience for the customer, but it requires building and testing the form. If you use a CRM trigger, the rep still initiates the quote, but everything after that point is automated.
Map your current quoting process against the seven nodes above. Where does it stall most often? That is the first place to build.
.png)
