FINANCE

Capture expense form submissions into the ledger

Accepts expense submissions from a webhook form, files the uploaded receipt to Drive, validates required fields and duplicate detection.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerExpense form submitted via webhookHTTP webhook
  • ActionStore receipt in monthly Drive folderGoogle DriveGoogle Drive
  • LogicValidate fields, cap, and check for duplicates
  • OutputAppend valid expense to reimbursement ledgerAirtableAirtable

What it does

Receives structured expense submissions from an intake form via webhook, stores the attached receipt in a dated Google Drive folder, and runs validation: required fields present, amount within single-item limits, and not a duplicate of a recent submission. Valid entries are appended to the reimbursement ledger; rejected ones return a reason to the submitter.

When to use it

Use this when you collect expenses through a form rather than email and want every submission normalized into one ledger automatically. It enforces complete data at intake so reviewers never deal with missing receipts or duplicate claims.

How it works

  1. 1A form submission hits the webhook trigger with expense fields and a receipt file.
  2. 2The receipt is uploaded to a Google Drive folder organized by month.
  3. 3Validation logic checks required fields, the per-item cap, and scans recent entries for duplicates.
  4. 4Failures return a rejection reason via the webhook response.
  5. 5Valid submissions are appended as a structured row to the reimbursement ledger.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.