AI AGENTS
Vendor Sanctions and Risk Screening Agent
Before approval, an agent researches a new vendor against sanctions and adverse-media sources, scores the risk.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor reaches Pending Screening in NotionNotion
- ActionSearch sanctions and adverse-media sourcesExa
- LogicSynthesize findings into a cited risk score
- ActionAuto-advance low-risk vendors to Cleared in NotionNotion
- OutputRoute flagged vendors to compliance Slack with evidenceSlack
What it does
Adds a compliance gate to onboarding. The agent takes a vendor's legal name and address, searches sanctions lists and recent news, weighs what it finds, and produces a risk decision with supporting links rather than a raw dump.
When to use it
When you must screen vendors for sanctions and reputational risk before paying them, and manual due diligence is the bottleneck holding up approvals.
How it works
- 1A new vendor reaching "Pending Screening" in Notion fires the trigger.
- 2The agent runs targeted searches across sanctions and adverse-media sources for the vendor's name and principals.
- 3It synthesizes findings into a risk score with cited evidence.
- 4A logic branch routes the result: low risk auto-advances to "Cleared"; medium or high risk does not.
- 5Flagged vendors generate a compliance review summary posted to Slack with the agent's evidence attached.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect ExaNeural search across the web.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.