SUMMARIZATION
Weekly export of Front decisions to a searchable Postgres registry
Each week, an AI processes all resolved Front threads, extracts structured decisions, and upserts them into a Postgres table that powers a queryable.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch Front threads resolved this weekFront
- ActionExtract normalized decision recordsOpenAI
- LogicDeduplicate against stable decision key
- OutputUpsert decisions into Postgres registryPostgres
What it does
Builds and maintains a durable, queryable decisions registry in Postgres. On a weekly schedule, the workflow gathers the week's resolved Front conversations, extracts each decision into a normalized record (subject, decision, owner, date, source thread), and upserts it into a Postgres table — deduplicating against decisions already captured so reruns stay idempotent.
When to use it
Use it when you want decision data you can actually query with SQL — joins against accounts, full-text search, or feeding a downstream dashboard — rather than scattered docs. Ideal for ops and data teams that already centralize on Postgres and need an auditable, long-lived decision history.
How it works
- 1A weekly schedule trigger fires.
- 2The workflow pulls all Front conversations resolved in the past week and their messages.
- 3An OpenAI model extracts a normalized list of structured decision records from each thread.
- 4A logic step deduplicates against a stable decision key so existing rows are updated, not duplicated.
- 5Records are upserted into the Postgres decisions table, ready for SQL search and dashboards.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.