All templates

Automated UpLead List Verification Checklist

Whenever you build a new target list in UpLead, WebRun checks how many of the contacts returned came back real-time verified, creates a Trello card to track the list's build-out with the verified count and any gaps, and posts a progress update to Microsoft Teams so the requester knows the list is ready to use.

Runs on WebRun · Strict Lockdown policy
Instantly, whenever a new UpLead list is built WebRunorchestrates each step
1 UpLead check the new list's verification results
2 Microsoft Teams post a progress update
3 Trello track the list build-out
In short

How do I turn a new UpLead target list into a verified prospect list?

WebRun checks every new UpLead target list the moment it's built, counting how many contacts came back real-time verified versus unverified. It creates a Trello card to track the list's build-out and posts a progress update to Microsoft Teams, so the requester knows exactly how ready the list is before using it.

  • Every new list gets a verified count before anyone starts working it
  • Thin segments get flagged instead of discovered mid-campaign
  • No credits are spent automatically, only reported on

Built for sales operations · SDRs · growth marketers · lead generation agencies

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.uplead.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    UpLead - check the new list's verification results
    uplead.com
    WebRun in UpLead: check the new list's verification results
    WebRun opens UpLead to check the new list's verification results.
    • Open UpLead and check the contacts returned by the newly built list
    • Count how many came back real-time verified versus unverified
    • Note which filters or segments returned the fewest verified contacts

    Done when The new list's verified and unverified counts are captured.

  3. 2
    Microsoft Teams - post a progress update
    microsoft.com
    WebRun in Microsoft Teams: post a progress update
    WebRun opens Microsoft Teams to post a progress update.
    • Post a progress update to the requester's channel: verified count and readiness
    • Flag any segment that came back thin so the filters can be adjusted

    Done when The requester has a Teams update on the new list's readiness.

  4. 3
    Trello - track the list build-out
    trello.com
    WebRun in Trello: track the list build-out
    WebRun opens Trello to track the list build-out.
    • Create a card on the Prospect Lists board for the new list
    • Include the total contacts, verified count, and any thin segments

    Done when The new list has a tracked Trello card.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.uplead.com
ScheduleRuns automatically on this cadence
Instantly, whenever a new UpLead list is built
DeliveryHow each run's result reaches you
List verification checklist · Microsoft Teams
OutputWhat each run produces - A tracked Trello card and a Teams progress update for every new UpLead target list.
Checklist
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it purchase or unlock additional credits automatically?

No. WebRun only reports on the contacts already returned by the list you built. Spending credits to unlock more contacts is a decision left to you.

What does real-time verified mean here?

Contacts UpLead confirms as deliverable at the moment the list is built, rather than a static database match. WebRun reports that verified count, it doesn't re-verify anything itself.

What happens if a segment comes back mostly unverified?

It's flagged in the Trello card and Teams update, so you know to adjust your filters rather than assuming the list is complete.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.