Start with notes you trust.
Supply notes directly for the first test. This recipe does not record or transcribe your meeting. A calendar event ending does not mean notes exist or are ready to read.
For recurring use, choose a notes source that your installed workflow pieces can access. Verify the source, account permissions and trigger in your own setup.
- A meeting title, date and participant names.
- Your notes or a transcript you are authorised to use.
- The agreed next steps and any confirmed dates.
- Your tone preferences and relevant company context.
Ask for a draft with clear boundaries.
A prompt to start with
Build a draft-only meeting follow-up workflow. Start from notes I provide. Extract decisions and next steps, including an owner and date only when the notes confirm them. Write a short follow-up in my tone. List anything I need to confirm separately. Return the draft for review. Do not send email or update other apps. Keep the workflow disabled until I test it.
Keep the unknowns visible.
Example input: Maya will share the onboarding checklist. You agreed to review it together, but no delivery date was confirmed. You will send two possible times for the next call.
A useful draft can thank Maya, mention the checklist and say you will send possible times. It should not invent a Friday deadline or claim that a calendar invitation has already been sent.
Hi Maya, Thanks for walking through onboarding with me. You’ll share the checklist, and we’ll review it together. I’ll send two possible times for our next call. Thanks! Before sending: confirm the checklist delivery date if one is needed.
Build a small process you can inspect.
Read the supplied notes
Keep the meeting identity and source attached to the input. Stop if the notes are missing.
Extract the commitments
Distinguish decisions from ideas. Leave an unknown owner or deadline unfilled.
Draft the message
Use the extracted facts and your writing preferences. Keep uncertain information outside the sendable text.
Return the draft to you
Review names, promises and dates. Sending the message remains a separate action in this first version.
Try the awkward cases before the next meeting.
These are acceptance criteria for your configured workflow, not a claim that every generated flow passes automatically. Inspect the actual step outputs and correct the workflow until it passes.
| Test input | Expected behaviour |
|---|---|
| Notes with a confirmed owner and date | The draft preserves both accurately |
| No deadline in the notes | No invented deadline |
| Missing or empty notes | Stops and asks for the input |
| Two contacts with the same name | Requests clarification before addressing a message |
| The same notes processed twice | No message sent; check duplicate handling before connecting any write action |
Add the trigger after the draft works.
Choose a supported trigger when your notes become available, then test its timing and duplicate behaviour. A scheduled check or supported notes-source event may fit better than a calendar-end event.
If you later add email sending, configure and test an explicit approval checkpoint on that path. A sentence asking the model to wait does not enforce a pause.
By the Jarvis team · Reviewed