CONTENT CREATION

Escalate stale linguist reviews from the Notion board on a daily check

Each morning, scan the linguist board for strings stuck In Review past their SLA and DM the assigned linguist.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily weekday morning schedule
  • ActionQuery linguist board for In Review cardsNotionNotion
  • LogicTier cards by idle time against SLA
  • ActionDM assigned linguist for idle cardsSlack
  • OutputEscalate overdue cards to lead in #localizationSlack

What it does

Keeps translation reviews moving. On a daily schedule it queries the linguist board for cards in the In Review state, measures how long each has been waiting, and nudges owners before strings go stale, escalating the worst offenders to a lead.

When to use it

Use it when translated strings pile up awaiting linguist sign-off and release dates slip. This replaces manual standup chasing with a consistent, tiered reminder so reviews finish on time.

How it works

  1. 1A daily schedule trigger fires each weekday morning.
  2. 2The flow queries the Notion linguist board for all cards with status In Review and reads their last-updated timestamps.
  3. 3A branch sorts cards into two tiers: idle 1 to 3 days versus overdue beyond 3 days.
  4. 4For tier-one cards it sends the assigned linguist a Slack DM with the string and a review link.
  5. 5For overdue cards it posts an escalation in #localization tagging the localization lead with the full overdue list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.