PERSONAL PRODUCTIVITY

Incoming Invite Triage Agent

On each new calendar invite, an agent researches the meeting context, decides whether to attend, delegate, or decline, drafts the response language.

CategoryPersonal Productivity
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew calendar invite receivedGoogle CalendarGoogle Calendar
  • ActionAgent gathers attendee and context dataGoogle CalendarGoogle Calendar
  • LogicReason over attend/delegate/decline
  • LogicDraft response language for chosen action
  • OutputPost recommendation and draft reply to SlackSlack

What it does

This is an agent-driven triage assistant for every incoming invite. Rather than applying fixed rules, the agent reads the invite, cross-references who's attending and your recent collaboration with them, infers the meeting's purpose from title and description, and produces a reasoned recommendation: attend, send a delegate, or decline with a polite reason. It drafts the actual reply text so accepting its suggestion is a single click in Slack.

When to use it

Use it when invites are ambiguous and a rules engine isn't enough — you want judgment about whether a meeting is worth your time and tactful language to bow out gracefully.

How it works

  1. 1A new Google Calendar invite triggers the agent.
  2. 2The agent gathers context: attendee list, organizer relationship, and meeting description.
  3. 3It reasons over whether the meeting needs you, a delegate, or no one, and selects an action.
  4. 4It drafts the response language for that action.
  5. 5The recommendation and draft reply are posted to Slack with approve/edit options.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.