FINANCE

Expense Submission Webhook Instant Triage and Routing

Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerExpense submission webhook receivedHTTP webhook
  • LogicGrade into in-policy, review, or violation
  • ActionDraft tier-appropriate decision messagingOpenAI
  • LogicBranch routing by tier
  • OutputRoute to Slack review or finance escalationSlack

What it does

This workflow is the routing brain for expense submissions. Your expense tool posts each new submission to a webhook, and the workflow grades it into one of three tiers. In-policy submissions are approved automatically, borderline ones open a manager review thread, and clear violations are escalated straight to finance with full context. One trigger, three deterministic paths.

When to use it

Use this when your expense system can fire a webhook on submission and you want every claim triaged the moment it's filed, with the riskiest ones never sitting in a queue. Works with any tool that can POST JSON.

How it works

  1. 1An incoming webhook delivers the submission payload (amount, category, employee, notes).
  2. 2A logic step grades it: within caps, marginal overage, or hard violation such as a blocked vendor.
  3. 3An OpenAI step drafts tier-appropriate messaging and a recommended decision.
  4. 4A logic branch directs the result by tier.
  5. 5The output posts to a Slack manager thread for review cases and to a separate finance escalation channel for violations.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  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.