CRM

Alert Slack when one friction theme spikes across Intercom accounts

On a daily schedule, this workflow scans recently closed Intercom conversations, detects when a single product-friction theme is suddenly affecting many accounts.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList conversations closed in last 24hIntercomIntercom
  • ActionClassify each thread's themeOpenAI
  • LogicAggregate counts and detect spike vs baseline
  • OutputPost ranked spike alert to SlackSlack

What it does

Once a day it gathers the last 24 hours of closed Intercom conversations, classifies each one's friction theme with an LLM, then counts themes across accounts to catch emerging spikes. If a theme jumps well above its recent baseline, it posts a Slack alert naming the theme, the affected accounts, and representative quotes.

When to use it

Use this to catch product regressions and confusing releases before they snowball — when a deploy or pricing change quietly generates a wave of similar complaints. Best for product and on-call teams who want a daily friction pulse rather than per-ticket noise.

How it works

  1. 1A daily schedule triggers the run each morning.
  2. 2The workflow lists conversations closed in the last 24 hours and pulls their transcripts.
  3. 3One LLM pass classifies every thread into a friction theme.
  4. 4A logic step aggregates counts per theme and compares each to its trailing baseline.
  5. 5If any theme breaches the spike threshold, a Slack message is posted with the ranked themes, impacted account names, and sample quotes.

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 SlackChannels, DMs, threads, mentions.
  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.