Flow Editor

The Flow Editor is the desktop workspace for building and maintaining a flow. It is where you place blocks on the canvas, connect paths, open block modals, review errors, save changes, and jump into related areas such as settings, enrollments, and history.

  1. Open Dashboard → Flows.
  2. Click a flow card or a flow row to open that flow in the editor.
  3. If the flow loads successfully, the editor fills the full screen. If loading fails, the page shows an error state with Try Again.
Note
The editor is designed for desktop browsers. On smaller screens, DripDrop shows a full-screen Desktop Only message instead of the editor canvas.
  • The canvas uses a visual node-and-connection layout. Blocks are placed by position and saved with the flow.
  • The background design comes from the flow settings. Confirmed background choices are Dots, Lines, Crosses, and Blank.
  • Snap-to-grid also comes from flow settings. When it is enabled, blocks snap while you arrange them.
  • The built-in controls help you move around the canvas. Fit-view is enabled so the editor can frame the flow when it loads.
  • Selecting a block opens the correct modal for that block type so you can edit its name and action-specific fields.

Left Side

Exit: Arrow in the top left corner. Returns to the dashboard flows tab. If you have unsaved changes, DripDrop opens an Unsaved Changes confirmation.

Right Side

Add Block: Opens the block menu.
Flow Enrollments: Opens the flow modal on the Enrollments tab.
History and events: Opens the flow modal on the History tab.
Flow Blocks: Opens the Blocks sidebar for navigation in larger flows.
Errors: Opens the Errors panel.
Save: Saves the current flow state.
Flow Settings: Opens the flow modal on the Settings tab.

Select Add Block to open the block menu.

The menu includes Pause, Text Message, Email, Notify, Conditional, A/B Split, Connection, AI, and End.

For more information on block types: Flow Blocks

Notify

Use Notify to send an internal email or SMS notification to fixed recipients. Configure the notification’s provider, template, sender, and recipient list.

  • Email notifications require an active email provider, email template, and sender.
  • SMS notifications require an active SMS provider, text-message template, and sender.
  • Enter recipients as email addresses or phone numbers, separated by commas or new lines.
  • If one recipient is invalid or suppressed, review the notification result rather than assuming every recipient failed.

Only active integrations and templates are available when configuring message-based blocks. If a provider or template is missing, confirm that it is active before returning to the editor.

Click the Pencil Icon on a block to open its modal. All block types require a block name. The rest of the fields depend on the selected block type. Save from the block modal to write the block configuration back into the flow.

Drag between block handles to create a connection. The editor applies a small set of confirmed connection rules before it allows the edge.

  • Pause → Pause is rejected.
  • Email → Email is rejected.
  • Avoid assuming any other connection rule unless you have confirmed it in source or by testing, because the current editor validation is intentionally narrow.

The Blocks sidebar helps when a flow gets large. Use it to review the list of blocks, jump the canvas to a specific block, or re-open a block for editing without hunting across the canvas.

Blocks sidebar open next to a multi block flow

Open the Errors panel to review flow validation before you save or activate a flow.

Errors

Errors identify missing or invalid configuration that needs attention. The panel groups errors by block and shows the block name when available.

  • To address errors: Open the named block, complete the required fields, then save the flow to run validation again.

Warnings

  • Warnings highlight configuration that should be reviewed but does not always prevent the flow from being saved.
  • Warnings can appear after creating a flow from a template when optional providers, senders, recipients, message templates, or custom fields were skipped. Review each warning before activating the flow.
  • When there are no errors or warnings, the panel shows All Clear. Use Save from the panel when you want to validate the latest flow configuration.
  • Select Save in the toolbar to save the current flow state.
  • Autosave runs every five minutes when autosave is enabled in the flow settings and the flow has unsaved changes.
  • The browser warns you before closing or reloading a page with unsaved changes.
  • When you select Exit with unsaved changes, choose Save & Exit to save first or Exit without saving to leave the current changes behind.

    Avoid Stale Changes

    Tip
    Use one browser tab for a flow whenever possible.

    If you reopen the same flow in another tab, save your work and refresh the tab you plan to continue using before making more changes. This helps ensure the editor is showing the latest saved version of the flow.

Enrollments, History, and Settings open in the full-screen flow modal without forcing you back to the dashboard. That makes it easier to inspect a flow, adjust it, and return to the canvas.

Editor Will Not Load

Refresh the page and select Try Again from the flow load error state.

A Provider or Template Is Missing

Only active providers and templates are available in message-based blocks. Confirm the provider and template are active in Integrations then return to the editor.

An AI Block Is Unavailable

AI blocks require an active AI integration and the account’s AI features to be enabled. Confirm the AI provider is active before adding or configuring the block.

A Block Is Marked Incomplete

Open the block and complete its required configuration. Template-created flows can show warnings when providers, senders, recipients, templates, or custom fields were skipped during setup.

Cannot Connect Two Blocks

Check whether you are trying to create an invalid connection, such as Pause → Pause or Email → Email.

Errors Remain After Saving

Open the block named in the validation panel, correct the required fields, and save again. Review warnings before activating the flow.