Unit21 Automated KYC Onboarding Kickoff
Every morning, WebRun opens Unit21 and reads customer entities created since the last run, builds a KYC onboarding checklist row in Google Sheets for each new entity, and posts an internal kickoff notice to the compliance Slack channel so analysts can begin customer due diligence on day one.
How do I automatically kick off KYC onboarding when a new customer is added in Unit21?
WebRun checks Unit21 every morning for newly created customer entities, builds a structured KYC onboarding checklist row in Google Sheets for each one, and posts an internal kickoff notice to the compliance Slack channel. Your team opens the day with a ready-to-work onboarding list so customer due diligence starts on day one, not day three.
- KYC onboarding begins within hours of a new customer being created
- Every new entity has a structured checklist before an analyst touches the file
- No new customer slips through without a compliance team member being alerted
Built for AML compliance teams · KYC analysts · fintechs · neobanks · BSA officers
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.unit21.aiin a real browser with your saved login - no setup, no API keys. -
1
Unit21 - read newly created customer entities
unit21.ai
WebRun opens Unit21 to read newly created customer entities. - Open Unit21 and navigate to the Entities section
- Filter for entities with a creation date since the last run
- Capture entity ID, name, entity type (individual or business), and assigned risk tier if set
Done when All new customer entities from the last run window are captured with their profile details.
-
2
Google Sheets - create KYC onboarding checklist row
google.com
WebRun opens Google Sheets to create KYC onboarding checklist row. - Open the KYC Onboarding Tracker sheet
- Add a new row for each entity: entity ID, name, type, risk tier, date created, and a checklist of required CDD documents
- Set the onboarding status to In Progress and leave the assigned analyst column blank for manual assignment
Done when A structured onboarding row exists for every new customer entity.
-
3
Slack - post internal kickoff notice
slack.com
WebRun opens Slack to post internal kickoff notice. - Post a kickoff notice to the AML compliance channel listing each new entity and its risk tier
- Include a direct link to the onboarding tracker row for each entity
- Remind the team to assign an analyst and begin document collection today
Done when The compliance team is notified of every new customer requiring CDD and can begin onboarding immediately.
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 contact the new customer about their KYC requirements?
No. WebRun only creates the internal checklist and notifies your compliance team in Slack. Any outreach to the customer is initiated manually by your team.
Does it assign an analyst automatically?
It leaves the analyst assignment blank in the tracker so your compliance manager can allocate workload. The Slack notice prompts the team to assign one immediately.
What if the same entity shows up multiple times?
It checks the onboarding tracker for the entity ID before adding a row, so duplicate entries are skipped even if the entity was created close to the run window boundary.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.