DOCUMENT OPS

Validate spreadsheets submitted via webhook before downstream processing

Accepts a spreadsheet via an HTTP webhook from an upload form, validates structure and rows synchronously.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSpreadsheet POSTed to webhook endpointHTTP webhook
  • LogicValidate headers against column contract
  • LogicValidate each row and collect errors
  • ActionArchive raw submission to DropboxDropboxDropbox
  • OutputReturn pass/fail JSON with error reportHTTP webhook

What it does

This workflow exposes an HTTP endpoint that an upload form or external system can POST a spreadsheet to. It validates headers and every row against your rules, then returns a structured response: accepted with a row count, or rejected with a detailed error list. It also files the raw submission in Dropbox for retention.

When to use it

Use it when a spreadsheet upload happens inside another product or portal and you want validation to be a synchronous gate — the submitter must get an immediate, machine-readable verdict rather than finding out hours later that their file was bad.

How it works

  1. 1An external system POSTs the spreadsheet to the webhook endpoint.
  2. 2Headers are checked against the required column contract.
  3. 3Each data row is validated; errors are accumulated per row.
  4. 4A branch decides accept vs. reject.
  5. 5The raw file is archived to Dropbox for the audit trail.
  6. 6A structured JSON verdict (status plus error list) is returned to the caller.

Set it up

What you configure once, before turning it on.

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