Primary navigation

Suggested
API Dashboard
Codex

Codex use case

Run event playbooks

Create repeatable workflows for event program management.

Difficulty Intermediate
Time horizon 1h

Use Codex with Slack, Google Drive, and Calendar to gather planning context, draft attendee-facing copy, and prepare a private checklist with owners, approvals, and open questions.

Best for

  • Community, developer relations, marketing, and operations teams running events.
  • Event pages, handoffs, and launch checklists where public copy and private operations need to stay separate.
  • Recurring event programs that need source-backed templates, owners, approvals, and open questions.

Contents

    ← All use cases

    Run event playbooks

    Create repeatable workflows for event program management.

    Use Codex with Slack, Google Drive, and Calendar to gather planning context, draft attendee-facing copy, and prepare a private checklist with owners, approvals, and open questions.

    Intermediate
    1h
    Try in the Codex app

    Use Codex with Slack, Google Drive, and Calendar to gather planning context, draft attendee-facing copy, and prepare a private checklist with owners, approvals, and open questions.

    Intermediate
    1h

    Related links

    Codex plugins Codex automations Use Codex in Slack

    Best for

    • Community, developer relations, marketing, and operations teams running events.
    • Event pages, handoffs, and launch checklists where public copy and private operations need to stay separate.
    • Recurring event programs that need source-backed templates, owners, approvals, and open questions.

    Skills & Plugins

    • Slack
      Read planning channels, threads, canvases, and decisions that define the current event scope.
    • Google Drive
      Gather approved templates, event docs, decks, recap notes, and launch assets.
    • Google Calendar
      Check event timing, deadlines, and meeting context while building the playbook.
    • Sheets
      Track tasks, owners, and deadlines in a structured format.
    Skill Why use it
    Slack Read planning channels, threads, canvases, and decisions that define the current event scope.
    Google Drive Gather approved templates, event docs, decks, recap notes, and launch assets.
    Google Calendar Check event timing, deadlines, and meeting context while building the playbook.
    Sheets Track tasks, owners, and deadlines in a structured format.

    Starter prompt

    Create a source-backed playbook for [event]. Sources to use: - planning channels or threads: [links or names] - approved docs, decks, sheets, or templates: [links or names] - calendar events or deadlines: [links or dates] Split the output into: - attendee-facing copy - private operating checklist - owner map - support plan or resources - approvals still needed - open questions - source appendix Do not publish anything or assume missing details. Put unknowns in open questions and keep private operations out of the public copy.
    Create a source-backed playbook for [event]. Sources to use: - planning channels or threads: [links or names] - approved docs, decks, sheets, or templates: [links or names] - calendar events or deadlines: [links or dates] Split the output into: - attendee-facing copy - private operating checklist - owner map - support plan or resources - approvals still needed - open questions - source appendix Do not publish anything or assume missing details. Put unknowns in open questions and keep private operations out of the public copy.

    Introduction

    When you have event programs to manage, for example our Codex community meetups, you often have context scattered across multiple sources:

    • The public event page
    • The program support plan
    • Slack messages
    • Sheets or documents
    • etc.

    You can use Codex to gather the approved planning sources and turn them into a playbook that separates attendee-facing copy from private operating details.

    Create your first playbook

    Use the starter prompt to ask Codex to generate an event playbook for you. It should:

    • Name planning sources (these could be links, internal tools, etc.)
    • List required information
    • Define rules for attendee-facing copy (keeping internal logistics out of it)

    You should get a list of things to check and run every time a new event is planned.

    Run the playbook as an automation

    After the first run of your new playbook works, keep the same thread open and ask Codex to run it as a scheduled automation.

    Review the new event requests. Check: - attendee-facing copy has no private logistics, budget notes, or internal-only partner context - asks are in line with the event program And give me a draft for follow up questions/checks I could send.

    Related use cases

    Coordinate new-hire onboarding

    Use Codex to gather approved new-hire context, stage tracker updates, draft team-by-team...

    Integrations Data

    Draft PRDs from internal context

    Use Codex with the $documents skill and connected apps such as Linear, Slack, Notion or...

    Integrations Knowledge Work

    Prepare meeting briefs

    Use Codex with Calendar, Drive, Slack, and Gmail to gather approved sources before a...

    Integrations Knowledge Work