Add a Ready or Reject Node
This guide shows you how to add a ready or reject node in a QuoteCloud workflow, allowing you to manage document approvals and ensure each outcome is handled correctly.
Steps to add ready and reject nodes
Understand approval workflow outputs
Approval nodes contain two separate workflow outputs: Approve and Reject . Approved documents follow the approval path, while rejected documents follow the rejection path.Add the reject endpoint
Under the rejection branch of the approval node, click the node placeholder labelled Add a step .Select “Reject to Send”
From the workflow action menu, choose Reject to Send to create the rejection endpoint for rejected documents.Add the ready endpoint
Under the approval branch of the workflow, click the node placeholder labelled Add a step .Select “Ready to Send”
From the workflow action menu, select Ready to Send to create the endpoint for approved documents.Review the workflow structure
Confirm that approved documents now route to the Ready to Send endpoint and rejected documents route to the Reject to Send endpoint.Complete the workflow setup
Once both endpoints are configured correctly, the workflow setup will be complete and ready for use.
FAQs
What is a "Ready" node and what does it do in a QuoteCloud workflow?
A Ready node marks a quote or record as prepared to move to the next stage of a QuoteCloud workflow. In sales quoting software and sales proposal software contexts, a Ready node signals that required validations, approvals, or preparations are complete so the item can proceed to downstream steps, be published, or trigger automated actions such as invoice creation or document publishing.
What is a "Reject" node and when should it be used?
A Reject node halts progression of a quote or proposal and flags it as not acceptable for further processing. Use a Reject node when a quote fails validation, violates business rules, needs corrections, or should be archived. In quote software workflows, Reject nodes typically end the current path or branch the workflow so the item can be returned for rework, corrected by the owner, or removed from active pipelines.
How do Ready and Reject nodes affect workflow state and downstream actions?
Ready and Reject nodes update the logical state of a workflow item: Ready advances the item toward completion while Reject halts or reroutes it. These state changes can drive status labels, access rules, reporting, and downstream automation in your proposal software. For example, a Ready node can trigger publishing, notifications, or QuickBooks syncing for invoicing, while a Reject node can open a corrective task, send a notification to the owner, or archive the record.
Who can add or edit Ready/Reject nodes in a workflow?
Typically only users with workflow creation or editing permissions—such as administrators, workflow designers, or designated power users—can add or modify Ready and Reject nodes. Granting these privileges to a small group helps maintain consistent business rules and prevents accidental changes to critical paths in your sales quoting software.
Do Ready or Reject nodes trigger notifications or automation?
Yes. Ready and Reject nodes can be configured to trigger notifications and automation rules. When a node changes state, it can send emails, internal alerts, update CRM statuses, generate documents, or start integrations (for example, syncing with accounting software). Configure the downstream actions in your proposal software to match your approval and escalation policies.
Can I revert a Ready or Reject decision once it has been set?
Yes—most workflows allow you to revert or move an item to a prior state, but the exact process depends on your workflow configuration and user permissions. Common approaches include creating a corrective branch, using a Reopen or Rollback action, or editing the node history. For auditability, consider recording who changed the state and why so you maintain a clear approval trail in your quote software.
What are best practices for using Ready and Reject nodes in sales quoting or proposal software?
Use clear naming and documentation for each node, validate data before marking a quote Ready, limit edit permissions to trusted users, and design explicit corrective paths for Reject decisions. Test workflows in a sandbox environment, include audit logging for state changes, and align node behavior with your CRM and accounting integrations to ensure consistent downstream actions.
How do Ready/Reject nodes work with integrations like QuickBooks Online or document-generation tools?
Ready nodes are often used as the trigger to publish documents, generate contracts, or sync transactions to accounting systems like QuickBooks Online, enabling invoice creation and financial recording. Reject nodes can block synchronization and instead trigger document revisions or archival. When configuring integrations, map Ready/Reject states to the desired actions—publish, sync, return for edits—so your sales proposal software and connected systems remain in sync.