Building a Flow

Two ways to build Flows: the setup wizard and form-based dashboard, or the visual Map view.

From the dashboard

The Flows dashboard is the fastest way to wire a Source to one or more Destinations and optionally add processing rules. Everything lives on one page, no canvas to navigate.

1
Open Flows
In the sidebar, click Flows. You'll see your existing Flows and a New flow button in the top-right corner.
2
Click New flow
Click New flow. A creation form slides in with the required fields.
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
Name the Flow
Give the Flow a descriptive name, something that reminds you what it does, like “TradingView → ICMarkets Live” or “TV scalper → Demo + Telegram”. The name appears in the Map view and on the Signals page.
5
Add Destinations
In the Destinations field, select one or more Destinations from the multi-select. Each selected Destination will receive a copy of every signal that passes through this Flow. You can add Destinations later by editing the Flow.
6
Optionally add rules
Expand the Rules section to add filter, transform, or score rules to the pipeline. Rules run top-to-bottom in the order they appear. See the Rule catalog for all available options.
7
Save
Click Save. The Flow is now active, the next signal from your Source will flow through it immediately.

Enable / disable without deleting

Every Flow has an Active toggle. Flip it off to pause delivery without losing your rule configuration or Destination list.

From the Map view

The Map view is a visual interface built on ReactFlow. It is best suited for visualising complex pipelines or fan-out patterns where seeing the connections as a graph is more intuitive than a form.

Here is how to build a Flow on the canvas:

1
Open the Map view
Click Flows in the sidebar, then switch to the Map tab. The canvas opens with any existing Flows already laid out as a graph.
2
Drag a Source node onto the canvas
From the left panel, drag a Source node onto the canvas and select the Source you want from the dropdown that appears.
3
Drag rule nodes between Source and Destination (optional)
Drag any rule nodes you want, filter, transform, score, and place them between the Source and your Destinations. You can reorder them by dragging.
4
Drag Destination nodes
Drag one or more Destinationnodes onto the canvas and select the Destination from each node's dropdown.
5
Connect the nodes
Drag a wire from the Source node's output handle to each rule or Destination. Connect rules to Destinations in order to define the pipeline.
6
Save
Click Save in the side panel. Signalync converts the graph into a Flow (or updates an existing one). The Flow is immediately active.

The Map view and the Flows list show the same underlying Flows, they are different views of the same data. A Flow created in the dashboard appears in the graph, and vice versa.

Testing your flow

The fastest way to verify a Flow is working is to fire a manual signal. Manual signals let you type a signal directly into the dashboard without needing a live TradingView alert or Telegram message.

1
Send a manual signal
Go to Sources, open your Source, and click Send test signal. Enter a minimal payload like EURUSD,buy,vol=0.01 and submit.
2
Watch the Signals page
Navigate to Signals. Your test signal should appear within a second. If the Flow has multiple Destinations, you will see a delivery count next to the signal row.
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, the Delivery shows filtered 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 for the toggle. If it is active, check whether a filter rule rejected the signal: open the Signal detail drawer; if a Delivery exists with status filtered, the rule name will be shown.

Some Destinations received the signal, others did not

Each Destination dispatches independently. Open the Signal detail drawer and compare the Delivery rows for each Destination. A Destination-specific failure (EA offline, webhook unreachable) shows as failed 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 or destination they affect. For example, if you use transform.symbol_map to rename GOLD → XAUUSD, it must appear above any filter.symbol_allow rule that checks for XAUUSD. Open the Flow editor, check the rule order, and drag to reorder if needed.