AI AGENTS
Attendee enrichment when an external invite lands
When a new calendar invite arrives with someone outside your company, researches that attendee and their employer and files a structured profile in a Notion meetings database.
How it runs
The automated pipeline, trigger to output.
- TriggerNew external calendar inviteGoogle Calendar
- ActionExtract attendee & company domain
- LogicSkip if profile already exists in NotionNotion
- ActionResearch attendee & companyExa
- OutputWrite structured profile to NotionNotion
What it does
As soon as a new external invite hits your calendar, the agent identifies the unfamiliar attendee, researches their professional background and current company, and writes a structured profile into a Notion database. Over time you build a searchable library of everyone you've met, with context attached to each meeting.
When to use it
You meet a lot of new people and want a durable, searchable record rather than a one-off message. Good for partnerships, BD, and recruiting where attendee context matters weeks later.
How it works
- 1A new external Google Calendar invite triggers the run.
- 2The agent extracts the external attendee's name, email, and company domain.
- 3It checks the Notion database to avoid creating a duplicate profile.
- 4Exa researches the attendee's role and the company's recent activity.
- 5The agent writes a structured page linking the attendee, company, and the upcoming meeting into Notion.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect ExaNeural search across the web.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.