REPRODUCIBLE WORKFLOW SPECIFICATION
Meeting-to-execution with Calendar, Gmail, Notion, and Linear
REVIEWED SEPTEMBER 2, 2026 / NOT A CUSTOMER PERFORMANCE CLAIM
Use one known calendar event as the source boundary, create a reviewable meeting record, and prepare follow-ups without inventing decisions or silently assigning work.
EXECUTION ORDER
Actions, purpose, and confirmation
- 01Google Calendar
get_eventResolve the exact event, organizer, attendees, and time zone.
No confirmation for the selected event read.
- 02Gmail
search_threadsRetrieve only the explicitly related pre-meeting context.
Confirm the bounded participants and query.
- 03Notion
create_pageCreate reviewed notes under the approved workspace parent.
Confirm parent, attendees, decisions, and final content.
- 04Linear
create_linear_issueCreate only explicitly agreed action items with a known team and owner.
Confirm each issue, owner, priority, and due date.
Verification checklist
- The event ID and participant list match the intended meeting.
- Notes distinguish recorded facts, decisions, and proposed follow-ups.
- Every Linear issue maps to an explicit approved action item.
- Created records return stable IDs and canonical links.
Known limitations
- This specification does not provide meeting transcription.
- Calendar attendance does not prove agreement with a decision.
- Email context should be tightly scoped.
- Assignments and deadlines require human confirmation.
How to run this workflow safely
Begin with discovery and read-only actions, then verify the selected accounts before any write. Ask for confirmation at the step where the workflow becomes externally visible, financial, destructive, or difficult to reverse. Keep the structured result from every action so the final response can separate completed work from skipped, rejected, or failed steps. Retry only operations that are safe to repeat or protected by an idempotency key.