Flexport Automated Denied Party Screening
Each time a new counterparty is added in Flexport, WebRun pulls the entity's name and country, checks it against denied-party and restricted-entity registers, logs every result in Google Sheets, and posts any flag to your compliance Slack channel for human review before the shipment is released.
How do I automatically screen new counterparties against denied-party lists?
WebRun checks each new Flexport counterparty against denied-party and restricted-entity lists as soon as they are added. It logs every result in Google Sheets for an audit-ready record, and posts any potential or confirmed flag to your compliance Slack channel so a human can approve or block the shipment before it moves.
- Every new counterparty is screened before a shipment proceeds
- Flagged entities are held for human review, never auto-released
- A timestamped audit log is maintained in Google Sheets for every screening
Built for trade compliance teams · importers · exporters · freight forwarders · supply chain compliance managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.flexport.comin a real browser with your saved login - no setup, no API keys. -
1
Flexport - detect new counterparty and pull details
flexport.com
WebRun opens Flexport to detect new counterparty and pull details. - Open Flexport and navigate to the new counterparty or shipment booking
- Capture the legal entity name, country, and any aliases
- Run the name through the denied-party and restricted-entity check in Flexport's compliance tools
- Record the match status: clear, potential match, or confirmed flag
Done when Every new counterparty has a screening result recorded.
-
2
Google Sheets - log screening result for every entity
google.com
WebRun opens Google Sheets to log screening result for every entity. - Append a new row with the entity name, country, screening date, and result
- Mark confirmed flags in red and potential matches in amber
- Keep the sheet as the audit-ready screening log
Done when The screening log row is written and colour-coded.
-
3
Slack - alert compliance team on any flag
slack.com
WebRun opens Slack to alert compliance team on any flag. - If the result is a potential or confirmed flag, post a message to the compliance Slack channel
- Include the entity name, country, flag reason, and a link to the Flexport record
- Leave the shipment on hold until the compliance team approves or rejects it. Never release a flagged shipment automatically
Done when Compliance team has been alerted and the shipment remains on hold pending review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it release a flagged shipment on its own?
No. WebRun holds the shipment and posts the flag to your compliance Slack channel for a human to approve or reject. Nothing proceeds automatically when there is a potential or confirmed denied-party match.
Which lists does it screen against?
It uses the denied-party and restricted-entity data available in Flexport's compliance tools, which cover major U.S. government lists. Your compliance team should confirm the lists meet your specific regulatory requirements.
Where is the screening history kept?
Every screening result is logged in a dedicated Google Sheets tab with the entity name, country, date, and outcome, giving you an audit-ready record for each counterparty.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.