OTHER

Screen pre-registered visitors against a watchlist before issuing a badge

When a visitor is pre-registered this checks their name and email against a security watchlist, then either issues a badge automatically or routes the request to security…

CategoryOther
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHost submits pre-registration formHTTP webhook
  • ActionLook up visitor against watchlistAirtableAirtable
  • LogicBranch: cleared vs flagged
  • ActionIssue badge and email cleared guestGmailGmail
  • ActionEscalate flagged match to security in TeamsMicrosoft Teams
  • OutputWrite screening audit rowAirtableAirtable

What it does

Adds a compliance gate to visitor pre-registration. Every guest is checked against a denied/flagged list before any badge is issued, so cleared guests get instant badges and flagged ones are escalated to security instead of slipping through.

When to use it

Use it in regulated or high-security sites where you must screen guests (former employees, denied parties, no-trespass list) before granting building access. Pairs with an Airtable watchlist your security team maintains.

How it works

  1. 1A host submits the pre-registration webhook with the visitor's full name and email.
  2. 2The flow looks up the visitor against the Airtable watchlist table by normalized name and email.
  3. 3A decision branch evaluates the match: clear, or flagged.
  4. 4If clear, a visitor record is created with status `Approved` and a badge token, and the guest is emailed their badge via Gmail.
  5. 5If flagged, no badge is sent; instead the flow posts the match details and host info to the security Teams channel for manual review.
  6. 6Either path writes an audit row to Airtable recording the screening decision and timestamp.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.