The App Ecosystem
Apps are the vocabulary of flows — the more you install, the richer your automations become
Every flow is ultimately a conversation between apps. When you write
/stripe payments today, you’re asking the Stripe app to go fetch data. When
you write /notify alert @finance, you’re asking the Notify app to ping
someone. Each /app action is a word in a language, and the more apps you
install, the richer your vocabulary becomes.
Flows are sentences. Apps are words. Install more apps, write more powerful
flows.
This page is your dictionary — every app, every action, what it does and how to
use it. But first, the concept that makes it all work.
How input and output work
This is the single most important thing to understand about app actions:
every step receives the previous step’s output as its input, and every step
produces output for the next step.
Actions accept natural language. You don’t need to worry about argument formats
or JSON — just describe what you want:
/github fetch issues labeled "critical" from myorg/myrepo
/stripe payments from enterprise customers this month over $500
Each action returns two things: a summary (human-readable text) and data
(structured results). Both flow to the next step automatically:
/stripe payments today
summarize totals by customer
/notify alert @finance
Here, Stripe’s payment data flows into the LLM step, which summarizes it, and
that summary flows into the notification. No wiring needed — it just works.
Source control and DevOps
These apps connect your flow to the systems where code gets built, shipped, and
monitored. A common pattern: fetch data from one, check status in another,
alert when something needs attention.
GitHub
/github subscribe myorg/myrepo
/github fetch open PRs from myorg/myrepo
/github fetch issues labeled "bug" from myorg/myrepo
/github sync myorg/myrepo
Vercel
/vercel status my-project
/vercel projects
/vercel domains my-project
/vercel env my-project
/vercel logs my-project
Railway
/railway status
/railway sync
/railway metrics
/railway logs
Sentry
/sentry issues
/sentry issue PROJECT-123
/sentry resolve 12345
/sentry stats
/sentry sync
Project management
Track work, manage issues, organize knowledge. These apps turn your flows into
automated project management — syncing status, creating issues from alerts,
and keeping your team’s tools in lockstep.
Linear
/linear fetch issues assigned to me
/linear fetch open issues in project CORE
/linear fetch issues closed this week
/linear create-issue Bug: login page broken
/linear sync
Notion
/notion search project roadmap
/notion query-db Tasks where status is "In Progress"
/notion create-page Meeting Notes for today
/notion databases
Business and payments
Revenue, customers, subscriptions — these apps give your flows financial
awareness. Build daily revenue reports, alert on large payments, track churn,
or sync customer data across systems.
Stripe
Stripe has the richest action set of any app, because financial data touches
so many workflows:
/stripe balance today
/stripe payments this week over $100
/stripe customers search john@example.com
/stripe subscriptions active
/stripe invoices unpaid
/stripe refunds pending
/stripe query how many new customers this month
/stripe sync
Infrastructure
DNS, CDN, analytics, caching — the plumbing that keeps your product running.
Flows that monitor infrastructure can catch problems before your users do.
Cloudflare
/cloudflare zones
/cloudflare dns A records
/cloudflare dns-set A record api.example.com to 1.2.3.4
/cloudflare dns-delete A api.example.com
/cloudflare analytics this week
/cloudflare workers
/cloudflare pages
/cloudflare purge all
/cloudflare purge https://example.com/page
Supabase
/supabase tables
/supabase count users
/supabase search active subscriptions
/supabase query show users who signed up this week
/supabase structure users
Communication
Flows aren’t just about data — they need to talk to people. These apps let
your flows send messages, emails, and notifications across platforms. Bridge
your team’s communication tools so an event in one place triggers a message
in another.
Slack
/slack send #general the deploy is complete
/slack channels
/slack history #engineering last 20 messages
Discord
/discord export #general last 100 messages
/discord curate #help-channel
Postmark
/postmark send email to john@example.com about the meeting tomorrow
/postmark activity
/postmark stats this week
/postmark templates
/postmark bounces
Notify
/notify the deploy is complete
/notify push new message from @cathy
/notify alert critical error in production
Chat
/chat message #general the deploy is done
/chat search error reports from this week
Analytics
Understanding what your users are doing, how your product is performing, and
where to focus next. These apps bring product analytics into your flows so you
can build reports, track trends, and react to signals automatically.
PostHog
/posthog events signups this week
/posthog persons john@example.com
/posthog insights conversion
/posthog flags
/posthog query count of signups by country this month
One Dollar Stats
/one-dollar-stats daily
/one-dollar-stats weekly
/one-dollar-stats monthly
/one-dollar-stats stats last 30 days
/one-dollar-stats pages last 7 days
/one-dollar-stats visitors
/one-dollar-stats pageviews
Built-in apps
These ship with every server — no installation needed. They’re the glue that
holds flows together: storing data, making HTTP calls, managing memory,
scheduling, and doing math.
Data
This one deserves special attention. The Data app is how flows persist
information — and that information is what powers
blocks on your dashboard. Every
/data upsert or /data series call writes to a shared data layer that blocks
can query and display in real time.
Think of it this way: flows produce data, blocks consume it. The Data app
is the bridge.
Use value= to store specific values, and type=, app=, category= to tag
entries for later querying from blocks:
/data upsert health-check type=stat value=up
/data upsert health-check type=stat value={status: up, latency: 120}
/data insert app=github category=ci-failures type=list
/data series stripe-revenue value={{payments.revenue}}
/data list type=metrics
/data query active users this week
Without value=, the Data app uses AI to extract a value from the pipeline
input. Specify value= explicitly for reliable storage.
The pattern is: flow steps produce data with /data, blocks query it with
query=. Once you see this loop, dashboards start to feel obvious.
Memory
/memory remember our deploy window is Tuesdays 2-4pm
/memory recall deploy schedule
/memory list
/memory forget deploy window
Google Calendar
/google-calendar today
/google-calendar now
/google-calendar sync
Fetch
/fetch get https://api.example.com/status
/fetch post https://api.example.com/webhook
/fetch health https://mysite.com, https://api.mysite.com
Webhook
/webhook create for deployment notifications
/webhook list
/webhook delete endpoint-id
Calc
llms.txt
Directory Scanner
Custom app actions
Everything above ships with start.chat or comes from the app marketplace. But
you can build your own apps with their own actions — and use them in flows
exactly the same way: /your-app action-name arguments.
View an app’s available actions in Server Settings > Apps.