CRM

Audit low-confidence Intercom topic labels into an Airtable review queue

Re-classifies stale Intercom conversations with OpenAI, and when confidence is low or topics conflict.

CategoryCRM
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule starts the topic audit
  • ActionPull stale-topic conversations from IntercomIntercomIntercom
  • ActionRe-classify topic and confidence with OpenAIOpenAI
  • LogicBranch on confidence and topic conflict
  • OutputWrite confirmed and needs-review rows to AirtableAirtableAirtable

What it does

Automated topic labeling is wrong often enough that blindly writing to your CRM creates new bad data. This workflow re-classifies older Intercom conversations, and any case where OpenAI is uncertain or returns conflicting topics is parked in an Airtable review queue with the transcript, suggested topic, and confidence. A reviewer confirms or corrects it; only confirmed labels proceed.

When to use it

Use it when data quality matters more than speed, such as before a major segmentation rebuild, or when an earlier automated backfill produced labels you no longer trust.

How it works

A schedule kicks off the audit. The workflow pulls conversations whose topic label is missing or older than a threshold from Intercom. OpenAI returns a topic and confidence. A logic branch sends high-confidence labels straight to the confirmed table, while low-confidence or conflicting ones go to a `needs_review` Airtable table. The output step writes both buckets to Airtable so a human can clear the queue.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.