CRM

Capture Email Signatures to a Role-History Warehouse

Parses every inbound email signature, normalizes the title and seniority, and appends an immutable row to Postgres so role changes over time can be tracked and queried.

CategoryCRM
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew inbound email receivedGmailGmail
  • ActionExtract raw signature fieldsOpenAI
  • ActionNormalize title to role and seniorityOpenAI
  • LogicSkip rows missing email or title
  • OutputAppend timestamped row to warehousePostgreSQLPostgres

What it does

This template builds the foundation the other workflows rely on: a clean, append-only history of who held which title and when. It parses each inbound signature, normalizes the title into a canonical role and seniority level, and writes one timestamped row per observation to a Postgres warehouse table.

When to use it

Stand this up first if you want signature-drift detection at all. It turns noisy, free-text signatures into structured, queryable role history. It is also useful on its own for tenure analysis and committee-change reporting.

How it works

  1. 1A new email arrives in Gmail and fires the trigger.
  2. 2An OpenAI step extracts the raw signature fields: name, title, company, phone, and email.
  3. 3A second normalization step maps the free-text title to a canonical role label and a seniority tier.
  4. 4A logic step skips rows missing a usable email or title so the warehouse stays clean.
  5. 5The normalized observation is appended as an immutable, timestamped row in Postgres.

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 PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.