CRM
Maintain a Postgres Signature-Drift Audit Log and Snapshot Title History
Records every parsed email signature into a Postgres history table, computes diffs against the last seen title per contact, and stores an auditable timeline of role changes.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled batch run of new emails since last executionOutlook
- ActionParse each signature into name, email, and titleOpenAI
- ActionQuery Postgres for latest stored title per contactPostgres
- LogicKeep only changed or new contacts
- ActionInsert versioned title-history row with diff and sourcePostgres
- OutputReport count of drift events capturedPostgres
What it does
This workflow turns signature drift into structured history. For each inbound email it parses the signature, looks up the contact's most recent stored title in Postgres, and when the title has changed it inserts a new versioned row capturing the before and after with a timestamp and source message ID.
When to use it
Use it when you need an audit trail rather than just a current value, for example to power churn analysis, to prove when a buyer changed roles, or to feed an org-mapping dashboard. It is the warehouse layer that sits underneath the CRM-writeback workflows.
How it works
- 1A scheduled run pulls the batch of new emails received since the last execution from Outlook.
- 2OpenAI parses each signature into a structured name, email, and title record.
- 3The flow queries Postgres for the latest stored title for each contact.
- 4A logic step keeps only contacts whose title changed or who are new.
- 5Postgres inserts a versioned history row with old title, new title, timestamp, and message ID.
- 6A run summary reports how many drift events were captured.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 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
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.