Visual workflows and private actions

Open Automations to build a connected workflow. The canvas and the step list edit the same saved draft. Current full-access workspace members can edit drafts; an owner or administrator must review publications that prepare portal links, selectable proposals or private team notices.

Arrange a branch without changing the other path

Choose Selected connection, then select a step type and Insert on selected connection. Inserting on a condition’s yes output leaves its no output unchanged. The new step continues to the original destination. Change either branch using the destination fields in the list.

Drag nodes to arrange them, or focus a node and use arrow keys; hold Shift for larger movements. Enter scrolls to that node’s fields. Pan, zoom and Fit all change the view. The list provides the same branch and step editing controls without dragging. Invalid connections are identified on the canvas and saving rejects loops, missing paths and unreachable steps.

Removing a step requires an explicit replacement for its incoming connections. Check both condition outputs afterward. Undo draft edit and Redo draft edit retain the last 50 local graph and position changes. They do not undo published versions or work already performed. The history lasts only in the current browser session.

Save positions only preserves the execution graph and its published revision. Save draft creates a new graph revision. If someone saved first, reload the current graph and layout before retrying; stale changes never silently overwrite them.

Review sources as well as the sample path

Save the draft, then enter sample facts under Rehearse before activation. Tags are case-sensitive. Try the other branch with a second set of sample facts. The selected path is highlighted and the review lists each local action’s source or recipients. Simulation creates no client records or messages.

Approve the exact saved revision. Its proposal sources and named recipients are frozen with the publication. Layout changes alone do not invalidate a graph review. Changed graphs, expired reviews, unavailable source images or changed authority require fresh review. Runs already started keep their original published version.

Prepare an existing portal link

Prepare existing portal link uses only the run’s explicitly linked wedding and its already-enabled project portal. It never creates, enables or sends a portal. Missing or disabled portals hold for review.

Open the prepared artifact and review it before copying. The preparation expires after 24 hours; the portal itself keeps its normal access policy. Disabling and re-enabling the portal, changing its link or changing the linked project invalidates an earlier preparation. Create a new reviewed run to prepare the new source. Portal tokens are not stored in workflow artifacts, receipts or events.

Prepare a selectable proposal

Prepare selectable proposal draft uses an exact published proposal version belonging to this business. It copies the frozen terms to one unissued draft on the run’s linked wedding. Source image availability is checked again. Later edits to the source proposal do not rewrite the selected version.

Open the resulting draft to review its packages, quantities, images and prices through the normal proposal workflow. This action issues no client invitation, agreement, invoice or payment. A plain document draft is a separate action and does not create selectable packages.

Notify named team members

Notify selected team members creates private in-app notices for the chosen full-access workspace memberships. It sends no email, SMS or push notification. Each recipient opens Your team notices to read and mark their own notices. Other workspace members cannot read these notices merely because they serve the same wedding.

If the publishing administrator or a recipient loses the necessary access before execution, the run holds without creating notices. Current membership is checked again when reading or marking a retained notice. Repeating a completed step does not create another notice or proposal.

Start from a real tag change or project conversion

A tag trigger matches an exact tag being added or removed through an authorized lead edit or merge. The event retains that transition even if someone changes the tags again before processing. Initial imports, direct database writes and existing historical tags are not treated as new changes.

A lead job created trigger starts only when an explicit lead conversion creates a new project and links that exact lead. Repeating the conversion does not create another trigger. A standalone project has no inferred lead or recipient. Relinking the lead before the event is processed does not redirect the earlier event to the new project.

Recover an interrupted operation

Reload a saved draft or run after a browser interruption. Retrying the same unchanged request reuses its receipt; changed details require a new request. Permission is checked again even for a replay. Existing artifacts retain their history. Review a held run’s current source, make a deliberate correction, and resume through the run controls. A damaged published snapshot remains a failed step until its source is repaired or a new reviewed workflow is created.

Provider configuration is unnecessary for these local actions. Email and SMS delivery still have their separate permission, cost, stop-policy and activation requirements.

Wait for a condition to become true

A condition step can now keep checking until it matches. Choose a current stage, tag or email-presence check, a recheck interval and a maximum wait. Matching proceeds through yes; reaching the original deadline while still unmatched proceeds through no. The durable run saves the first deadline, so retries, worker restarts and pauses do not extend it. Existing reply, booking, payment and closed-lead stop rules still apply before every check. Choose those rules to fit your intended workflow.

Simulation shows the immediate yes path for matching sample data or the timeout/no path for unmatched sample data. Form-answer conditions refer to a saved run snapshot; use a form-submission trigger when new answers must start new work.