AI AGENTS
Meeting-Request Auto-Booker from Email
Detects scheduling requests in incoming email, finds an open slot on your Google Calendar, books it, and emails a confirmation with the invite — no back-and-forth.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email arrives in GmailGmail
- ActionExtract meeting intent and proposed timesOpenAI
- LogicFilter: keep only scheduling requests
- ActionCheck calendar availabilityGoogle Calendar
- LogicBranch: book slot or offer alternatives
- ActionCreate event and invite senderGoogle Calendar
- OutputSend confirmation replyGmail
What it does
When someone emails asking to meet, the workflow extracts the proposed times and duration, checks your real availability, picks the best matching slot, creates the calendar event with both parties, and sends a confirmation reply. If no proposed time fits, it offers your next three open windows instead.
When to use it
When you field a steady stream of "can we grab 30 minutes this week?" emails and want them booked automatically against your actual calendar, including conflict checks, without a scheduling-link tool.
How it works
- 1A new Gmail message triggers the run.
- 2OpenAI determines whether the email is a meeting request and extracts duration, attendees, and any proposed times.
- 3A filter stops the run for non-scheduling email.
- 4Google Calendar is queried for free/busy across the candidate window.
- 5A branch books the first proposed slot that's open, or composes three alternatives if none fit.
- 6Google Calendar creates the event and invites the sender.
- 7A confirmation reply is sent from your Gmail account.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect OpenAIModels, embeddings, files.
- 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
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.
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.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.
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.
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.
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.