CRM

Detect Contact Role Changes from Email Signature Drift

Watches inbound Gmail for signature blocks that differ from the title on record in Attio, and flags contacts whose job title has changed so the buying committee stays accurate.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew inbound email receivedGmailGmail
  • ActionExtract name, title, company from signatureOpenAI
  • ActionLook up contact in Attio by emailAttio
  • LogicCompare extracted title vs stored title
  • ActionUpdate title and archive prior roleAttio
  • OutputNotify account owner of role changeSlack

What it does

Every inbound email carries a signature block. When a contact's title in that block drifts from the title stored in your CRM ("Manager" becomes "Director", "VP" becomes "SVP"), this template catches the change, confirms it is a real promotion or move rather than a formatting quirk, and updates the contact record in Attio.

When to use it

Run this when your buying-committee data goes stale between deals. Titles change constantly inside target accounts, and a stale title silently misroutes outreach and weakens forecasting. This keeps role data fresh without a single manual edit.

How it works

  1. 1A new email arrives in the monitored Gmail inbox and fires the trigger.
  2. 2An OpenAI step parses the signature block and extracts name, title, and company.
  3. 3The contact is looked up in Attio by email address.
  4. 4A logic step compares the extracted title against the stored title and decides if the drift is a meaningful role change.
  5. 5On a real change, Attio is updated with the new title and the prior title is archived to a history field.
  6. 6A Slack message notifies the account owner of the role change.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AttioReal-time CRM with structured data + powerful views.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.