CRM
Compute a Stakeholder Influence Graph and Store It in Postgres
Aggregates every email thread on a deal, builds a weighted who-replies-to-whom influence graph, scores each stakeholder's centrality.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule per open deal
- ActionRetrieve all deal threadsGmail
- LogicBuild weighted reply-direction edge list
- ActionLabel nodes and resolve alias addressesOpenAI
- LogicCompute centrality and influence scores
- OutputUpsert committee graph snapshot to PostgresPostgres
What it does
Produces a quantitative influence graph of a deal's buying committee. Instead of just labeling roles, it measures interaction volume and reply direction across all threads to rank who actually drives the conversation, then stores the structured graph for downstream reporting.
When to use it
Reach for this when you want hard data behind committee dynamics across many deals, feed a deal-health dashboard, or compare influence patterns between won and lost opportunities.
How it works
- 1A weekly schedule kicks off the run for each open deal.
- 2Gmail retrieves all threads associated with the deal and its participants.
- 3The flow tallies messages, replies, and addressing direction to build a weighted edge list between participants.
- 4OpenAI labels each node with a role and resolves duplicate or alias addresses to single people.
- 5Centrality and influence scores are computed per stakeholder from the edge weights.
- 6The ranked nodes and edges are upserted into Postgres committee tables, replacing the deal's prior snapshot.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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.
Dormant Account Anniversary Re-engagement Email
Each day, finds Attio accounts whose last activity was exactly N months ago and sends each owner's contact a personalized re-engagement email from Gmail.
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.
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.
