The cockpit
for background work
Workers, triggers, and connections in one place. Driven by Claude, Codex, Cursor, or any agent that speaks MCP. One operating layer.
See a live demo/workers. Floom discovers each one.Declare connections: [gmail] in worker.yml. Floom injects the live token at run time. No secrets in code.
[fetch] 12 threads · [summarize] 12/12 · [draft] 4/12 · [save] 314 lines
output.json · 4 drafts saved to gmail
09:00:01 INFO · 09:00:09 ✓ completed in 8.2s
name: gmail_intake_brief
runtime:
type: python
runner: e2b
trigger:
type: schedule
cron: "0 9 * * MON-FRI"
# connections
- gmail (depontefede@gmail.com)
One worker file. Every trigger reads the same thing.
A worker is a folder with worker.yml plus your code. Declare the trigger, secrets, and connections. Floom handles cron, webhooks, manual runs, and the MCP surface from the same file.
Every connection, fresh. Every run, on the record.
Workers reuse the same OAuth token Floom holds for each service. No secrets in code, no expired tokens silently failing in cron. Stream logs live; export every run to CSV with one click.
See observabilityYour agent creates the worker. Floom runs it.
Install one MCP server and Claude, Cursor, or any agent can callworkers.create, schedule a cron, or trigger a run. Skip the canvas. The brief is the workflow.
Spin up a worker in two minutes.
The cockpit for every background task you direct. Triggered by cron, webhook, or your agent.
See a live demo