Assistant
System Map

The whole data plane on one canvas

Triggers fire workflows. Workflows call connectors and the scraper. Results flow back as outbound webhooks, messages, files, or rows.

Mini Map
Node legend
Trigger (orange)Anything that starts a run: cron, webhook, email, form, file, manual.
Workflow (pink)The pipeline runner. Routes events, calls steps, handles retries.
Connector (blue)Authenticated bridge to an external API (AI, comms, data, payments).
Scraper (amber)Firecrawl modes — scrape, search, map, crawl. Returns markdown/JSON.
Webhook out (green)Outbound HTTP / Slack / email notifications.
Output (grey)Terminal sinks: DB row, file, message.
Edge payloads
eventNormalized envelope: { id, source, occurred_at, payload }.
invokeTyped step input → connector call. Retried with backoff.
fetch URLWorkflow → Firecrawl request (URL, mode, schema).
markdown / jsonCleaned content returning to the workflow context.

Request lifecycle

  1. Step 1
    Trigger fires
  2. Step 2
    Event normalized
  3. Step 3
    Workflow routed
  4. Step 4
    Connectors / Scraper invoked
  5. Step 5
    Result merged into context
  6. Step 6
    Outputs written

Drill into a subsystem

Wireframes only — no live runs from this canvas.