Delete Node

The Delete node guide explains how to remove a node from a QuoteCloud workflow, including the official UI steps, confirmation prompts and system messages you will encounter. It also highlights important cautions and considerations so you can safely edit approval and automation flows in your sales quoting software or sales proposal software.

Follow the step‑by‑step procedure shown on the Delete node page in the QuoteCloud user guide. That page describes the exact UI actions to take, the confirmation prompts you will see, and any system messages generated when the node is removed from your quote software or proposal software workflow.

Before deleting a node, confirm downstream dependencies, active triggers, linked actions, and any conditions that reference the node. Test the change in a sandbox or a duplicate workflow where possible, and consider exporting or backing up the workflow configuration so you can restore settings if needed.

Recovery or undo options depend on your QuoteCloud setup and are documented on the Delete node guide. Some accounts offer version history or a recycle/restore feature; in other cases a deleted node may need to be recreated manually. Check the official documentation for the exact recovery options available to your organization.

Permissions and role requirements for modifying workflows are managed by your QuoteCloud account settings and administrative controls. Only users with the required admin or workflow‑edit privileges can remove nodes—refer to the Delete node page to confirm which roles in your organization have authority to modify workflows in your quote software or proposal software.

The product documentation explains how QuoteCloud handles connections, triggers and downstream logic when a node is removed. In some cases references will be automatically updated or removed; in others you may need to rewire triggers and actions manually. Review the guide to learn the exact behavior so your automation and approval paths remain intact.

Yes—removing a node can change approval routing, break automation triggers or alter downstream actions. It may also affect how historical workflows are interpreted. To avoid disruption, review impacted flows, test changes in a sandbox, notify stakeholders and back up the workflow configuration before applying edits in your production sales quoting software or quote software.

Best practices: map dependencies first; export or back up the workflow; test the deletion in a sandbox or duplicate workflow; update any conditions, triggers or linked actions that referenced the node; document the change and notify affected users; and confirm you have the necessary admin permissions to make the edit in your sales proposal software or proposal software environment.