Your first useful Bot workflow: turn notes into an action list

Start with a job you can check in a few minutes. Turning a short set of notes into an action list is a good first workflow because you can compare every result with the original. The goal is a usable list, not a demonstration of how much text an assistant can write.

Prepare the input

Choose notes you are allowed to share. Remove unnecessary private details. Include the meeting date and enough context to distinguish decisions from suggestions. You can supply text directly; this workflow does not require a calendar or project-management connection.

For this illustrative exercise, use: “Monday review: Deniz will send the revised proposal on Thursday. We might test a second pricing option. The customer still needs to confirm the delivery address.”

Run the workflow

Ask for actions, open questions, and proposals as separate groups. Require a source phrase for every action. An absent owner or date should stay absent. Do not ask the assistant to add tasks to another system yet.

Prompt to copy

Turn the notes below into a reviewable action list.
Use columns: action, owner, explicit due date, source phrase.
Then list open questions and unapproved proposals separately.
Write "not specified" for missing owners or dates.
Do not create tasks, send messages, or infer commitments.
Notes: [paste the notes]

Review a worked example

The proposal is an action owned by Deniz with Thursday as the stated deadline. The second pricing option is a proposal, not an approved task. The delivery address is an open question. If the assistant assigns the address question to a colleague or invents a date, correct it before using the list.

Check every row against the notes. If Thursday needs a calendar date, confirm the intended week rather than guess.

If one sentence contains two actions, check whether both survived extraction. If an action is conditional, keep the condition attached to it. “Send the proposal after approval” must not become an immediate send task. Ask for a revision of the affected row rather than a fresh summary that may introduce new changes.

Use it again

Try a second set of notes and record any repeated mistakes. Add a concrete rule only when it applies beyond one example. Keep the reviewed list as your output; direct writes to a task system require a separate connection and permission decision. Explore Golub Bot or discuss a connected workflow when you know which step should come next.