Automated Jumio Verification Results Digest
Every morning, WebRun opens Jumio, checks new identity verification submissions from the last 24 hours, exports the full results to Google Drive, and posts the daily digest of approved, failed, and pending verifications to Slack.
How do I get a daily digest of Jumio identity verification results?
WebRun checks Jumio every morning for identity verification submissions from the last 24 hours, exports the full results to Google Drive, and posts a daily digest of approved, failed, and pending outcomes to Slack. It only reads verification outcomes, so reviewing a flagged case stays with your team.
- Verification outcomes are visible every morning without logging into Jumio
- Failed and pending cases are never lost in the queue
- Manual review decisions always stay with your compliance team
Built for compliance teams · KYC analysts · fraud and risk teams · onboarding operations
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
www.jumio.comin a real browser with your saved login - no setup, no API keys. -
1
Jumio - check verification submissions
jumio.com
WebRun opens Jumio to check verification submissions. - Open the Jumio dashboard and check submissions from the last 24 hours
- Read each verification's outcome: approved, failed, or still pending review
- Note the reason for any failed or flagged verification
Done when Every submission from the last 24 hours has a read outcome.
-
2
Google Drive - export the results
drive.google.com
WebRun opens Google Drive to export the results. - Open the verification results folder in Google Drive
- Export today's results with outcome and reason for each
- Keep prior days' exports on file for reference
Done when Today's full results are saved to Google Drive.
-
3
Slack - post the daily digest
slack.com
WebRun opens Slack to post the daily digest. - Post the daily digest to the compliance or onboarding Slack channel
- Break it down by approved, failed, and pending counts
- Leave any manual review decision to your compliance team
Done when Today's digest has been posted to Slack.
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 WebRun approve or reject a verification?
No. WebRun only reads outcomes that Jumio has already determined. Reviewing a flagged or failed verification stays with your compliance team.
Does WebRun see the actual ID documents or biometric data?
No. It only reads the verification outcome and reason code Jumio surfaces, never the underlying document image or biometric data.
What happens to pending verifications?
They're included in the digest as pending so your team knows what still needs manual review, but WebRun does not push a decision on them.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.