Skip to Content
Custom WorkflowsBuilding Workflows

Building Workflows

You build workflows by talking to your assistant. Describe what you want, your assistant creates it, you try it out, and you iterate together until it’s exactly right. Then set it on a trigger or a schedule and let it run.

How it works

  1. Tell your assistant what you want — Describe the workflow in your own words
  2. Your assistant builds it — It creates the workflow, picks the right tools, and writes the instructions
  3. It’s live immediately — Ask your assistant to run it so you can see what it does
  4. Iterate together — Tell your assistant what to change, run it again, repeat until it’s right

Getting started

  1. Go to Workflows in Town
  2. Type what you want in the composer at the top
  3. Your assistant takes it from there

What to say

Just describe what you want in plain language. The more specific you are, the better the result:

Good examples:

  • “I want a workflow that watches for bill notifications and extracts due dates and amounts”
  • “Create a workflow that sends me a weekly digest of all newsletters I received”
  • “Build something that reminds me about GitHub PRs waiting for my review after 24 hours”
  • “When I get a meeting invite, research the attendees and send me a prep brief”

Less helpful:

  • “Make an email workflow” (too vague — what should it do?)
  • “Handle my inbox” (what specifically?)

Include what should trigger the workflow (every new email, daily at 8 AM, when a meeting starts, etc.) and what it should actually do. Your assistant will figure out the rest.

What your assistant builds

When you describe a workflow, your assistant creates the full configuration:

  • Name and description — So you can find it later
  • Instructions — What the workflow does, step by step
  • Triggers — When it runs
  • Tools — What actions it can take (read emails, add labels, search the web, etc.)
  • Mode — Whether actions run automatically or wait for your approval

You can see everything your assistant is building in the configuration preview on the left side of the screen.

Iterating together

This is where it gets powerful. After your assistant creates the first version, you keep talking:

  • “Make it run at 8 AM instead of 6 AM”
  • “Actually, don’t archive newsletters from The Morning Brew”
  • “Add the ability to search the web for company info”
  • “Change it so sending emails requires my approval”
  • “The summary should be shorter — just bullet points”

Your assistant updates the workflow each time. You can accept the changes or ask it to try again.

You can also click into the configuration preview and edit settings directly — toggle tools on or off, adjust triggers, or tweak the instructions by hand.

Seeing it in action

Once your assistant creates a workflow, it’s live right away. To see how it behaves, just ask your assistant to run it:

  • “Run the bill tracker now”
  • “Try running my weekly digest”

You’ll see exactly what the workflow does — what emails it reads, what labels it applies, what it sends. If something’s off, tell your assistant what to change and have it run again.

This is the fastest way to iterate: create, run, adjust, repeat.

After creation

Your assistant can keep modifying workflows after they’re live. Just ask:

  • “Change my bill tracker to also flag invoices over $500”
  • “Make my weekly digest run on Fridays instead of Mondays”
  • “Stop my PR reminder from pinging me about draft PRs”

You can also manage workflows from the detail page:

  • View run history
  • Edit settings
  • Enable or disable
  • Run manually

Tips

Start simple. Get the basic version working first, then add complexity. It’s easier to refine something that’s close than to get it perfect on the first try.

Be specific about edge cases. “If an email is both a newsletter and from a known contact, keep it in inbox.” Your assistant handles these well when you spell them out.

Run it to see what happens. After your assistant creates a workflow, ask it to run right away. You’ll see exactly what it does and can adjust from there.

Start with approval-required mode. You can always switch to autonomous later once you trust the behavior.

Example conversation

You: I want a workflow that watches for receipts and invoices, extracts the amount and vendor, and adds them to a “receipts” label.

Assistant: Done — here’s what I’ve set up:

  • Triggers on every incoming email
  • Looks for receipts and invoices
  • Extracts vendor name and amount
  • Adds the “receipts” label

[Configuration appears on the left]

You: Also archive them after labeling.

Assistant: Updated. The workflow will now archive emails after adding the receipts label.

You: Run it and show me what happens.

Assistant: Done — it found 2 receipts from yesterday, labeled them “receipts”, and archived both.

You: Perfect. But don’t archive receipts over $500, I want those in my inbox.

Assistant: Updated. Receipts over $500 will be labeled but stay in your inbox.

Last updated on
Manual ConfigurationHow It Works