Skip to content
PLEXON AI
Theme
Download

Analyst

Stay on top of a portfolio without staring at charts

“Either I watch the market all day or I miss the move.”

A board that is quiet until something happens, fed by scheduled runs, with a note written to the journal each time.

  1. Turn on the Trader persona

    It arrives with its cockpit board, its workflows and its data sources already attached.

    Personas

    Install the Stock Trader persona from the marketplace, switch to it, and open the live Trader Cockpit board it brings along.
    What happens in this clip
    1. Find the Stock Trader persona in the marketplace and install it.
    2. Switch to it from the persona picker.
    3. The welcome screen and the starter prompts change with it.
    4. It brings its own dashboard, the Trader Cockpit, already live.
    5. Switching back leaves the persona installed for next time.
  2. Point it at your data

    Import an OpenAPI spec or build the endpoints by hand. API key, Bearer, Basic or OAuth 2.0, with a per-endpoint test runner.

    API Connections

    The API Connections panel: bring any REST API in with a base URL and auth, like NASA FIRMS, OpenAQ, and OpenSky here, then call it from chat
  3. Put the cockpit up

    Stat tiles, charts and tables, refreshed on a timer or in the background.

    Try this

    Build me a board for <your watchlist>: a stat tile per position, a chart of the last 90 days, and a table of today movers. Refresh it every 15 minutes.

    Dashboards

    The Weather board opened in edit mode, widget by widget: the board parameter every card reads, where each one gets its data, and how often it refreshes.
    What happens in this clip
    1. The Weather board opens in edit mode.
    2. A board parameter at the top is read by every card on it.
    3. Each widget shows where it gets its data.
    4. Each one carries its own refresh interval, in plain language.
    5. Change the parameter and every widget re-runs.
  4. Check on a clock, not on a whim

    A job on a cron expression, auto-disabled after three consecutive failures so a broken feed does not spam you forever.

    Dynamic Workflows

    A workflow open on the canvas: an inbox trigger, a tool step that reads the email, an AI step that pulls out a mobile number, a condition that branches on whether the number is known, then a WhatsApp hello, a notification and a step that reads the reply, with a step rail on the left grouped by what each one does.
  5. Only speak when there is something to say

    A condition step decides whether the run ends silently or sends.

    Try this

    Add a condition so the run ends silently unless something moved more than 3 percent. Only then send me a message.

    Dynamic Workflows

    A bundled workflow opened in the editor, one step at a time: the trigger that polls the inbox, the tool step that reads the email, the AI step and the fields it returns, the branch, the message it sends, and the notification at the end.
    What happens in this clip
    1. A bundled workflow opens in the editor.
    2. The trigger at the top polls the inbox.
    3. A tool step reads the email, spending no AI tokens.
    4. An AI step pulls out named fields, and a branch decides what happens next.
    5. A message step sends the reply, and a notification step tells you it went.
  6. Hear about it wherever you are

    The message arrives on your phone and the reply continues the same session.

    Telegram Bot

What you end up with

A quiet board and a message when something moves. Educational only: it never places an order.

Download Plexon

Also for analyst