IT OPS

Route shared-mailbox email by sender domain and intent to vendor or internal queues

Combines sender-domain rules with LLM intent classification to split shared-mailbox email into vendor, internal-staff, and unknown-sender ClickUp queues with the right SLA tag.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email in Outlook shared mailboxOutlook
  • LogicMatch sender domain to vendor/internal lists
  • ActionClassify intent with OpenAIOpenAI
  • LogicResolve queue and SLA from class plus intent
  • OutputCreate tagged ClickUp task in resolved queueClickUpClickUp

What it does

Not all email should be treated the same based on content alone — who sent it matters. This workflow looks up the sender's domain against your known vendor and internal-staff lists, classifies the intent, and routes to a different ClickUp queue for each combination, tagging the task with the SLA that applies to that sender class.

When to use it

Use it when your shared mailbox receives mail from vendors, internal staff, and the public, and each group needs a different queue, owner, or response time. Helpful for keeping vendor escalations out of the general support pile.

How it works

  1. 1A new email arrives in the Outlook shared mailbox.
  2. 2A logic step matches the sender domain against vendor and internal allowlists.
  3. 3OpenAI classifies the intent of the message.
  4. 4A second logic step combines sender class plus intent into a target queue and SLA tag.
  5. 5A ClickUp task is created in the resolved queue with the SLA tag and sender class applied.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ClickUpDocs + tasks + chats in one workspace.
  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.