CRM
Build Org Hierarchy from Calendar Meeting Attendees
After each customer meeting, reads the Google Calendar attendee list and inferred speaking roles.
How it runs
The automated pipeline, trigger to output.
- TriggerCustomer meeting ends in Google CalendarGoogle Calendar
- ActionRead attendees, organizer, and required flagsGoogle Calendar
- ActionInfer reporting hierarchy from signalsOpenAI
- LogicDetect new or more-senior stakeholders
- OutputUpdate Attio relationships and flag new contactsAttio
What it does
Every time a customer meeting ends, this workflow inspects the Google Calendar event's attendee list, organizer, and optional/required flags to infer a reporting hierarchy among the people in the room. It detects when a new senior stakeholder joins a recurring meeting and updates the Attio relationship graph so the account team sees an accurate, current org chart instead of a stale one.
When to use it
Use it when expansion or renewal accounts keep adding new faces to calls and your CRM never catches up. It is ideal for customer success and account management teams who measure relationship depth across a buying group.
How it works
- 1A Google Calendar event-ended trigger fires for meetings tagged to a customer account.
- 2The workflow reads the attendee list, organizer, and required-versus-optional status.
- 3An OpenAI step ranks attendees into a likely reporting hierarchy using organizer signals and meeting cadence.
- 4A logic branch checks whether any attendee is new or more senior than known contacts.
- 5New stakeholders and reporting links are written to Attio, and an output step flags genuinely new senior contacts for the owner.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect AttioReal-time CRM with structured data + powerful views.
- 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 CRM workflows
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
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.