FeaturedFinance Ops#Deepfake Fraud#Payment Fraud#Business Email Compromise#Vendor Verification#Accounts Payable#Human Review

Deepfake Vendor Payment Change Triage

Cross-check urgent vendor payment change emails, require human review, and block social engineering signals before money moves.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Deepfake Fraud#Payment Fraud#Business Email Compromise#Vendor Verification#Accounts Payable#Human Review

Click a node to select it — same as the Heym editor; the panel shows its settings.

11 nodes · Free & source-available

Deepfake Vendor Payment Change Triage

Protect accounts payable from business email compromise and deepfake-assisted payment fraud. The workflow watches a dedicated mailbox, looks up the vendor record through an internal API, and pauses for human review before classifying the request.

What this workflow does

  1. PaymentChangeMailbox receives vendor bank detail change requests
  2. BuildPaymentReviewPacket extracts sender, subject, and message context
  3. LookupVendorRecord retrieves approved contacts and current payment metadata
  4. ReviewPaymentChangeRisk assesses urgency, channel mismatch, impersonation, and verification gaps
  5. RoutePaymentDecision separates blocked, verified, and callback-required requests
  6. Blocked requests alert the fraud team in Slack
  7. Verified decisions are archived in DataTable
  8. Ambiguous requests email an internal callback owner

Use cases

  • Deepfake payment fraud prevention
  • Vendor bank account change verification
  • Business email compromise triage
  • Accounts payable human approval workflows

Setup

Connect the monitored IMAP inbox, your internal vendor master API, an LLM credential, Slack, DataTable, and email. The agent must request human review. Never use contact details from the inbound message for verification, and never let this workflow move money.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym