Reference
Flows
Reusable routines that run on a schedule or on demand, with persistent working memory.
Flows automate frequent multi-step tasks. A flow is a reusable named routine — Surfboard executes it on demand or on a schedule, and builds memory across runs. Examples:
- Writing an investment proposal — research the company, pull in your notes, and assemble them into a draft
- Drafting a spec — start from a one-page description, research supporting customer information, scan the codebase, generate screenshots or wireframes
- Researching a blog post — gather sources, propose topics, create an outline, review with you, and publish
Every flow has two parts:
- Instructions – The operational prompt that tells Surfboard what to do each run. Editable at any time.
- Memory – Working content that persists between runs. Surfboard reads it at the start of each run and updates it at the end — useful for tracking prior findings or context that builds over time.
Creating a flow
- Ask Surfboard: "Create a flow that summarizes my Slack DMs every morning" — it will walk you through the steps.
- Or turn an existing board or document into a flow. If a document already has the right instructions, ask Surfboard to "turn this document into a flow."
Finding your flows
Your flows appear on your home page. You can also ask Surfboard to list them at any time.
Running a flow
- Type
~in the chat bar — it autocompletes to your list of flows. - Or open a flow's page and click Run.
- Scheduled flows run automatically on their cadence.
Run history
Open any flow's page to see the full history of past runs.
When to use a flow vs. a task
- Task: You need it once, right now (a prep brief before a meeting, a drafted email).
- Flow: You need the same multi-step thing repeatedly, and want it to build on what it learned last time.
Try these prompts:
- "Create a flow that pulls my top 5 action items from Slack and email every Monday morning"
- "Turn this customer research doc into a flow I can run for any new account"
- "List my flows"