SUMMARIZATION

Curate a per-objection coaching playbook page in Notion from the clip library

An agent reviews the growing objection clip library, groups clips by objection type.

CategorySummarization
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionPull clips and scores from the libraryCodaCoda
  • LogicGroup clips by objection category
  • ActionDraft per-category playbook guidanceOpenAI
  • OutputUpdate Notion playbook pagesNotionNotion

What it does

Goes beyond logging clips and actually authors the coaching curriculum. On a schedule, an agent reads the objection library, clusters clips by category, identifies what separates high-scoring responses from low-scoring ones, and updates a Notion playbook page per objection type with recommended framing, example lines, and links to the strongest clips.

When to use it

Use this once your library is large enough to find patterns and you want a maintained playbook rather than a raw clip dump. Ideal for enablement leads who want the team's best practices written down and kept current automatically.

How it works

  1. 1A schedule triggers the agent run (e.g., weekly).
  2. 2The agent pulls the latest clips and scores from the Coda library.
  3. 3It groups clips by objection category and reasons about what distinguishes strong from weak handling in each.
  4. 4For each category it drafts updated guidance: recommended approach, example phrasing, and links to top clips.
  5. 5It writes or updates the matching Notion playbook page, preserving manual edits where possible.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.