Building a Flow

Two ways to build a Flow: the form on the Flows page, or the visual Map view.

From the dashboard

The Flows page is the fastest way to wire a Source to one or more Destinations and optionally add processing Rules. Everything lives in one simple form, no canvas to navigate.

  1. 1

    Open Flows

    In the sidebar, click Flows. You'll see your existing Flows and a New flow button at the top of the page.
  2. 2

    Click New flow

    Click New flow. The creation page opens with the required fields.
  3. 3

    Pick your Source

    Select the Source you want this Flow to listen to from the dropdown. If you haven't created a Source yet, go to Sources first and come back.
  4. 4

    Name the Flow

    Give the Flow a descriptive name, something that reminds you what it does, like “TradingView to ICMarkets Live” or “TV scalper to Demo account”. The name appears on the Flow card and as the wire label in the Map view.
  5. 5

    Add Destinations

    In the Destinations list, tick one or more Destinations. Each selected Destination receives a copy of every signal that passes through this Flow, and you can add more later by editing the Flow. MT5 accounts and HTTP webhooks are the Destination kinds you can connect today; Telegram channel and Discord webhook Destinations are coming soon.
  6. 6

    Optionally add Rules

    In the Rules section, add filter or transform Rules to the pipeline. Rules run top to bottom in the order they appear. See the Rule catalog for all available options.
  7. 7

    Create the Flow

    Click Create flow. The Flow is active immediately: the next signal from your Source will flow through it.

Enable / disable without deleting

Every Flow has an Active toggle, on the Flow card and on its detail page. Flip it off to pause delivery without losing your Rule configuration or Destination list.

From the Map view

The Map view is a visual canvas. Your Sources and Destinations appear as nodes, and every Flow is drawn as a labeled wire between them. It's best suited for seeing fan-out patterns at a glance, when a graph is more intuitive than a form.

Here is how to build a Flow on the canvas:

  1. 1

    Open the Map view

    Click Flows in the sidebar, then switch to the Map tab. Sources line up on one side of the canvas and Destinations on the other, with your existing Flows already drawn as wires. Destination nodes show a live connection status.
  2. 2

    Draw a wire

    Drag a wire from a Source node's handle to a Destination node. A side panel opens with a new Flow prefilled for that pair.
  3. 3

    Configure the Flow in the side panel

    Name the Flow, tick any additional Destinations, and optionally add Rules. Rules live inside the Flow and are edited in this panel; they are not separate nodes on the canvas.
  4. 4

    Create the Flow

    Click Create flow. The Flow is active immediately and appears on the canvas as a wire labeled with its name and Rule count.
  5. 5

    Edit by clicking a wire

    Click any existing wire to reopen the side panel with that Flow loaded. Click a node to see the details of the Source or Destination behind it.
The Map view and the Flows list show the same underlying Flows, they are different views of the same data. A Flow created on the Flows page appears in the graph, and vice versa.

Testing your flow

For a quick dry run, open your Flow's detail page and use Simulate Flow: enter a symbol, action, and volume, then click Run simulation. For each Destination you'll see whether the signal continues or gets filtered, the signal values after your Rules ran, and the name of the Rule that stopped it. It's a simulation only, nothing is dispatched.

To verify real end-to-end delivery, fire a manual signal. Manual signals let you type a signal directly into the dashboard without needing a live TradingView alert.

  1. 1

    Send a manual signal

    Open Signals and click Send a signal. Pick the Source your Flow listens to, enter a minimal payload like EURUSD,buy,vol=0.01, and send it.
  2. 2

    Watch the Signals page

    Your test signal appears at the top of the Signals list within a moment, with an overall status showing whether it was routed to all, some, or none of its Destinations.
  3. 3

    Inspect Deliveries

    Click the signal row to open the detail drawer. Each Delivery is listed with its Destination name, status badge, and dispatch latency. If a Rule filtered the signal for a particular Destination, that Delivery shows a Filtered status and the name of the Rule that rejected it.

Troubleshooting

Signal arrived but no Deliveries

Check that the Flow is Active: open the Flows page and look at the toggle. If it is active, check whether a filter Rule rejected the signal: open the signal's detail drawer; if a Delivery shows a Filtered status, the name of the Rule that rejected it is listed right on the Delivery row.

Some Destinations received the signal, others did not

Each Destination dispatches independently. Open the signal's detail drawer and compare the Delivery rows. A Destination-specific failure (for example, the Receiver EA for that MT5 account being offline) shows a failed status with an error message on that Delivery row only; other Destinations are unaffected.

Rule config did not apply

Rules run in order, top to bottom. Transform Rules must come before the filter Rule they affect. For example, if you use transform.symbol_map to rename GOLD to XAUUSD, it must appear above any filter.symbol_allow Rule that checks for XAUUSD. Open the Flow editor, check the Rule order, and use the arrow buttons to reorder if needed.