DOCUMENT OPS
Duplicate receipt detection with Slack alert
On each new receipt, checks BigQuery for an existing record with the same vendor, date, and amount and posts a Slack alert when a likely duplicate or double-submission is found.
How it runs
The automated pipeline, trigger to output.
- TriggerNew receipt row written to BigQueryBigQuery
- ActionQuery BigQuery for matching vendor, date, and amountBigQuery
- LogicBranch on whether a likely duplicate was found
- ActionPost side-by-side duplicate alert to SlackSlack
- OutputTag row as pending-review in BigQueryBigQuery
What it does
Catches duplicate expense submissions before they get reimbursed twice. For every receipt parsed into BigQuery, it queries for prior rows matching the same vendor, date, and total within a small amount tolerance, and routes any match to a Slack channel for a human to confirm or dismiss.
When to use it
Use it when the same receipt gets submitted from two devices, forwarded twice, or re-uploaded after a failed sync. Finance teams run this to stop double payments and to spot employees accidentally claiming the same expense across reports.
How it works
- 1A new parsed receipt record arriving in BigQuery triggers the check.
- 2An action queries BigQuery for earlier records with the same vendor and date and a total within the configured tolerance.
- 3A logic step decides: zero matches means clean, one or more means a suspected duplicate.
- 4On a suspected duplicate, a Slack message posts both records side by side with confirm and dismiss actions.
- 5The original record is tagged in BigQuery as pending-review so it is excluded from spend totals until resolved.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.