# Workflows for work you repeat

> Do a job once with Construct, then save it as a workflow you can test, run by hand or on a schedule, or start when an email or a file arrives.

Do it once in chat, then run it any time.

Do a job once with Construct, then ask it to save the steps as a workflow. It tests the workflow before anything goes live, doing every read for real and holding back each email and change for you to look at.

## Set it up

1. **Do the job once**: Ask Construct for the work in plain words and check what comes back, so the steps you keep are ones that already worked.
2. **Save it as a workflow**: Ask it to save what you just did. Construct writes the steps, tests them and shows you a draft with what it would have sent.
3. **Choose what starts it**: Run it by hand or on a schedule, or start it when a file lands in a folder, an email arrives from someone you list, or another tool calls its private link.

## Things to ask

Each link opens Construct with the words ready to send.

- [Every Monday at 9, sum up last week's sales and email them to my team](https://construct.computer/?prompt=Every%20Monday%20at%209%2C%20sum%20up%20last%20week%27s%20sales%20and%20email%20them%20to%20my%20team)
- [When a new invoice lands in my Invoices folder, add it to my expenses sheet](https://construct.computer/?prompt=When%20a%20new%20invoice%20lands%20in%20my%20Invoices%20folder%2C%20add%20it%20to%20my%20expenses%20sheet)
- [Save what we just did as a workflow I can run again](https://construct.computer/?prompt=Save%20what%20we%20just%20did%20as%20a%20workflow%20I%20can%20run%20again)
- [Every morning, check my GitHub repos for new issues and tell me which need me](https://construct.computer/?prompt=Every%20morning%2C%20check%20my%20GitHub%20repos%20for%20new%20issues%20and%20tell%20me%20which%20need%20me)

## What to expect

- **It asks before it sends**: A workflow that sends or changes anything stays a draft until you press Save, and those steps ask you again every time or once a run, as you choose.
- **Every run on record**: Each workflow keeps its recent runs and its versions. Open a run to see what every step did, or go back to an earlier version.
- **Edits wait their turn**: A change becomes a new version that waits for Save while the old one keeps working, and a run that has started finishes the way it began.
- **Shared with your team**: In a team, anyone can run a workflow on their own connected accounts, and only the person who made it or an admin can change it.

## More use cases

- [Scheduled jobs](https://construct.computer/use-cases/scheduling/): Morning briefings and Monday reports that run with your laptop closed.
- [Research](https://construct.computer/use-cases/research/): Questions answered in a table, a doc or a spreadsheet, with sources.
- [Email](https://construct.computer/use-cases/email/): An agent with a mailbox that reads, drafts and replies when you say so.
- [Memory](https://construct.computer/use-cases/memory/): It remembers what you teach it and shows you everything it knows.
- [Team apps](https://construct.computer/use-cases/internal-tools/): A tracker or a booking app for your team, built by asking.
- [Teams](https://construct.computer/use-cases/team-workspaces/): One crew for the whole team, with roles and shared work.
- [Discord, Telegram and Slack](https://construct.computer/use-cases/channels/): Mention an agent where your team already talks.
- [Voice calls](https://construct.computer/use-cases/voice-calls/): Call an agent from the browser and plan your week out loud.

---

The Markdown copy of https://construct.computer/use-cases/workflows/. Everything Construct Computer publishes is listed in https://construct.computer/llms.txt.
