Nothing else competes for attention here — no counters, no recent activity.
Integrations → Connectors, filtered by connection state, auth type and visibility.
Left: what you configure. Right: exactly what your customer sees.
Activity → Events, the inbound and outbound record.
Every customer using your embedded integrations; this workspace has only a test one.
General is where Settings opens for an Owner — organisation identity first, joining rules second.
Agent is the first item under Integrations; Home's prompt box opens the same place.
The Diagram tab draws the workflow from the code — it is read-only, and it cannot drift.
Use contract fills ctx.input with a sample built from the workflow's own contract.
Three trigger types. A workflow with no trigger only runs when you call it.
Agent is the first item under Integrations in the sidebar. Home's prompt box opens the same place.
A session in progress. The rail on the left is your history; every session keeps its full conversation.
One card per pending call. Each shows the exact tool name and the exact arguments.
The session opens with your message at the top. The agent's tool runs collapse into Worked · 3 steps — Show details expands them.
A Manual-mode approval gate. One card per pending call, each showing the exact tool and payload.
The plan (right) and the build tracker (middle). Nothing has been built yet — the counter reads 0/6.
Two phases complete. Workflows is mid-flight, its three substeps named. Note the chip now reads Auto.
Import and Create connector sit top-right; the chips filter by All, Connected, OAuth and visibility.
The version tile reads In test, not published — the connector works, but no customer can reach it yet.
The providers link opens the OAuth apps sitting behind that method.
Create connector stays disabled until the name is filled — the footer says so.
The icons on each card are the providers currently serving that category.
Nothing is connected here yet, and the endpoints are listed anyway — they exist per entity, not per provider.
The Auth column shows the raw internal values — OAUTH and INPUT here. A connector with no catalogue entry shows its raw ID instead of a name.
Connect GitHub and Create workflow sit top-right; the pills filter by execution tier. Every row's live cell is an em dash — nothing is deployed.
The editor with code editing enabled — Configuration left, workflow.js centre, the tool tabs right.
Deploy to environment sits under Publish snapshot, with the latest version noted beneath it.
Until you run it, the result pane just reads Hit Run to execute without saving.
Every action chip carries its pinned version, such as getSale V1.1.
Both editors sit on JSON here; the Schema view holds the generated contract.
Generated from the deployment you are actually calling — copy the curl from here rather than from docs.
The dismissible What triggers do banner explains all three types before you pick one. The Schedule column shows the cron each trigger compiles to.
Each option carries its own one-line description — reproduced nowhere below, so read them here.
Routes are required — a webhook with none has nowhere to send its payload.
Advanced options start collapsed; the defaults shown here suit most senders.
Interval is the default mode, and the timezone defaults to your browser's.
The connector cannot be changed after the trigger is created — choose it deliberately.
Nothing outstanding — the handled count is the only sign anything ever landed here.
Agent confidence and provenance sit under the text; here no patch could be derived automatically.
Connect to Claude sits under the build prompt on Home, below the suggestion chips.
Configure on the left, see exactly what the customer sees on the right.
The preview redraws as you type — that header text is exactly what appears above it.
Status colours stay fixed whichever base you pick, so failed always reads as failed.
The live preview keeps rendering the customer's view while you flip these.
The preview follows the selected user — pick one and the panel shows that customer's real connection state, not a mock-up.
Each variant expands to the exact snippet for the user you selected.
Events is where a debugging pass starts — did the thing arrive at all?
Auto refresh, top-right, is off by default.
Turn on failure alerts creates the two alerts most teams need in one click.
Firing history at the bottom reads This alert has not fired yet.
A daily 3 PM schedule failing the same way every day — the pattern the Workflow filter is for.
The second line under each name is the identifier you will see again as endOrgId.
Change role is greyed out on the Owner's own row.
Two capabilities are called out as role-gated rather than grantable: using the AI assistant and reading the audit log.
The role selector only preselects what a joiner gets; it is not a ceiling.
The Key column shows only a prefix and the last four characters, with a copy icon.
The dialog spells out that Test is a separate credential, not a sandbox.
The panel scrolls past what is shown here — an Environment selector follows Customer.
The Configs page before any config exists. Read a config from workflow code with fastn.envConfig.get("key").
What a workspace looks like before anyone adds a stage: one built-in Live target and no review gate in front of it.
The choice is exclusive and it is a redirect, not a migration — rows already written stay where they are.
Before anything is registered. The empty state repeats the whole concept, scopes included.
Rows marked not measured have a cap but no usage reading behind them.
Filters for people, actions, types and a date range sit above the table, with Export top-right.
The paragraph underneath warns that widgets are deleted immediately and cannot be restored here.
The sign-in address is read-only here because an identity provider manages it.
Every workflow's API tab shows its own endpoint and a copyable curl.