Skip to main content

⚙️ Bots

No. You can start running bots as soon as your exchange connection is active.
Adding a contract is only needed to access on-chain analytics (Holders, Alerts, Sell Pressure).
Bots operate directly through your exchange API connection, not through smart contracts.
  1. Go to Exchange Connections and add API keys.
  2. Open Bots → Overview and choose a strategy.
  3. Configure spread, depth, order size, and refresh interval — then start the bot.

    Once launched, the bot immediately begins quoting on the exchange with your selected parameters.
Market-Making: continuously provides buy/sell liquidity to tighten the spread and stabilize the market.
Support-Level: protects key price levels by placing liquidity walls below support zones.
Treasury-Building: accumulates token inventory or builds reserves using algorithmic accumulation logic.
→ Details: Market-Making, Support-Level, Treasury-Building.
Yes — you can run several bots at the same time, as long as they operate on different pairs or have non-conflicting logic.
For example, you can run one Market-Making bot to manage liquidity and another Support-Level bot to defend price levels.
Avoid overlapping orders on the same pair to prevent internal collisions.
Once your bot is launched, the system automatically tracks its Target and Current parameters.
You’ll see how the bot performs relative to your defined configuration:
Target Spread / Current Spread
Target Depth / Current Depth
Filled Orders, Executed Volume, Open Orders

This allows you to monitor how close your live orderbook state is to the intended setup and adjust parameters if needed.
No. Flow Terminal provides automation and analytics tools, but you are fully responsible for how bots are configured and what funds are used.
Always define a clear risk allocation for each bot — only use funds you are comfortable risking.
The platform does not guarantee profitability or compensate for losses resulting from strategy settings or market movements.
The bot automatically detects lost connectivity and transitions to Suspended state.
It will stop placing or managing orders until a valid connection is restored.
You’ll be notified via system alerts and Telegram (if connected).
Each plan or workspace may include a maximum active bot limit based on performance capacity.
If you reach your limit, you’ll need to stop an existing bot or upgrade your workspace to launch more.

📊 Analytics

From on-chain sources (holders, transfers, contracts) and connected exchange feeds.
Minor data delays are possible depending on chain/network speed.
Methodologies and data windows differ.
Flow Terminal prioritizes on-chain truth and verified exchange feeds.
Yes — add the token’s contract for that chain separately.
Each contract operates as an independent analytics scope.

🔔 Alerts

Yes. Built-in types: Whale Transfer, Exchange Inflow, Exchange Outflow, Sell-Pressure Touch.
→ Manage them in Analytics → Alerts.
In Alerts, set minimum amounts (Token / USD) or a × multiplier for Sell-Pressure events.
Tune them to match your trading volume and volatility.
Raise or lower thresholds, or disable certain alert types in Manage Alerts.

📨 Telegram

Go to Integrations → Telegram, authorize the bot, then Send test.
Choose the chat/channel where you want messages delivered.
• Use Send test.
• Ensure the bot is in the chat with post permissions.
• For private groups, invite the bot and select the correct destination.

🎯 Events

A private trading session you configure — no public leaderboards or open rewards.
You set the exchange, pair, prize pool, and duration.
Go to Events → Setup, define exchange, pair, pool, and timeline.
Track progress through Created → Active → Finished stages in the UI.

🔍 Troubleshooting

No data after adding a contract: initial sync may take time — refresh or verify address.
Telegram silent: check bot permissions and resend test.
Too many alerts: raise thresholds or disable types.
CSV import fails: use UTF-8 CSV with headers: address,title,category,sell_probability,comment.
Visit Support or contact the team with details:
contract, network, exchange, and a short description of the issue.