Add a Node

A node is a single step or element on the workflow canvas that represents an action, decision, wait, or other discrete part of a process. In QuoteCloud, nodes define the sequence and logic that moves quotes, proposals, invoices or tasks through your approval and document workflows.

Open the workflow editor and use the canvas controls (usually a '+' or Add Node control) to place a new node. After placing it, select the node type, complete the configuration form (name, settings and any required fields), then save the node so it appears on the canvas and can be connected to other steps.

When adding a node you typically set a node name and node-specific options such as action details, decision conditions, assigned users or roles, and timing parameters (waits or timeouts). Complete and save the node form so it becomes active in the workflow.

After adding and saving a node, connect it by drawing or creating a link between its connector point and existing nodes—usually by dragging from a connector or using the editor's connection tool. That link defines the flow from one node to the next and any conditional logic between them.

Common node types include action nodes (perform an operation), condition/decision nodes (branch based on rules), wait/timer nodes (pause until a condition or timeout) and integration/event nodes (trigger external actions). The exact types available depend on your QuoteCloud environment and workflow engine.

Yes. Adding or modifying nodes usually requires workflow edit permissions or workflow ownership. QuoteCloud environments commonly enforce role-based access controls and audit logging, so only users with the appropriate role can change approval paths or node configurations.

Yes—depending on your QuoteCloud setup, nodes can trigger integrated actions such as generating documents, syncing transactions to QuickBooks Online, or sending data to other systems. Use integration or event-type nodes to automate steps between your sales quoting software, sales proposal software and connected accounting or document tools.

Use clear, descriptive names for nodes and keep steps small and focused. Reuse common nodes or sub-workflows where possible, add timeouts and fallback paths, and assign roles (not just individuals) for maintainability. Test changes in a staging environment, document workflow versions, and keep approval flows as simple as possible to reduce errors in your quote software and proposal software processes.