FINANCE

Route drafted accruals through a controller approval gate

When a draft accrual entry is created in Airtable, sends the controller an approve/reject prompt in Microsoft Teams.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew pending accrual row in AirtableAirtableAirtable
  • ActionSend approve/reject card to TeamsMicrosoft Teams
  • LogicBranch on controller decision
  • ActionPost approved entry to ledger via webhookHTTP webhook
  • OutputMark Airtable status Posted or Needs reworkAirtableAirtable

What it does

This workflow is the approval layer for drafted accruals. Each time an accrual entry lands in the Airtable review queue, it asks the controller to approve or reject in Teams, and only approved, balanced entries get pushed to the downstream ledger — keeping a clean audit trail of who signed off.

When to use it

Pair it with any accrual-drafting workflow once you need segregation of duties: the system proposes, a human disposes. Use it when auditors require evidence of review before journal entries hit the books.

How it works

  1. 1A trigger fires when a new row with status "Pending" appears in the Airtable accrual queue.
  2. 2An action posts an adaptive card to Microsoft Teams showing the entry's debits, credits, and supporting source so the controller can decide.
  3. 3A logic step branches on the controller's response.
  4. 4On approve, an action posts the balanced entry to the ledger system over an HTTP webhook and flips the Airtable status to "Posted".
  5. 5On reject, the output marks the row "Needs rework" with the controller's note for the preparer.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  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.