Sanctions-screen new vendors the moment they submit your intake form
When a vendor submits your Typeform intake, screen them against global sanctions and debarment lists, log the verdict in Airtable, and alert procurement on Slack.
Integrations
Typeform
OpenSanctions
Airtable
Slack
Type
Categories
- Operations
- Finance
Build an agent workflow that screens every vendor against global sanctions and debarment lists the moment they submit our intake form, so procurement never has to manually run names before contracting.
Trigger: a Typeform webhook on a new response to our vendor / supplier intake form.
When the webhook fires, the agent should do the following:
1. Parse the Typeform payload and extract the company legal name, country of incorporation, and every named person on the form (signatories, beneficial owners, primary contact). For each person, pull any date of birth and address fields the form collected.
2. Call OpenSanctions Match Entities (Screening) once against the default collection, batching all queries into a single request: one Company query for the vendor itself, and one Person query for each signatory or beneficial owner. Use threshold 0.7 unless the company name is very common, in which case tighten it. The default collection covers sanctions, PEPs, debarment, and criminal watchlists in one pass.
3. Classify each entity as one of: Clear (no matches above threshold), Review (matches between 0.7 and ~0.85 or only soft signals), or Hit (high-confidence match on sanctions, debarment, or crime datasets). Note which datasets triggered for each match. Roll the worst per-entity result up into one overall vendor verdict.
4. In Airtable, Create Records in our "Vendor Screening" base with one row per submission. Capture: submitted company name, country, overall verdict (Clear / Review / Hit), the top match score, the datasets that triggered (e.g. "sanctions, debarment"), the OpenSanctions entity URLs for every match found, and the Typeform submission ID for traceability.
5. If the verdict is anything other than Clear, Send a Slack Message to the #vendor-onboarding channel tagging our procurement lead. The message should be a short plain-English summary: which vendor, why it needs review (e.g. "signatory matches a politically exposed person on the EU PEPs list" or "company appears on the World Bank debarment list"), the top match score, and a link to the Airtable row. If the verdict is Clear, do not send any Slack message.
Keep the screening logic deterministic: the agent should follow the threshold and verdict rules above rather than making judgment calls about who is risky. Human review of Review and Hit results happens in Slack and Airtable.
What it does
- Fires the second a vendor submits your Typeform intake, before anyone on your team reads the form.
- Pulls the company name, country of incorporation, and every signatory or beneficial owner listed on the form.
- Screens each one against global sanctions, politically exposed persons, procurement debarment, and criminal watchlists from OpenSanctions.
- Logs every submission in your Airtable Vendor Screening base with the verdict, top match score, and which dataset triggered.
- Pings procurement in Slack only when a vendor needs human review, so clean vendors keep moving without noise.
What you’ll need
- A Typeform account with a vendor or supplier intake form already collecting responses.
- An OpenSanctions API key (their paid plans cover commercial procurement use).
- An Airtable base with a Vendor Screening table ready to receive rows.
- A Slack workspace and the channel you want review alerts posted to.
How to customize it
- Tighten or loosen the match threshold. The default catches close matches; raise it if very common names create noise.
- Choose which datasets count as a hit. Procurement teams often weight debarment lists as heavily as sanctions; financial-services teams lean on PEPs.
- Change the Slack channel or the procurement lead who gets tagged on every review.
- Add extra fields to the Airtable row, such as estimated contract value, requested department, or contact email, so reviewers have full context in one place.
Use cases
- Onboarding Automation
- Notifications & Alerts