HR & RECRUITING

EAD Auto-Extension Eligibility Triage

For EAD work permits nearing expiry, this workflow checks auto-extension eligibility rules, separates employees who are auto-covered from those who must file.

CategoryHR & Recruiting
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery BigQuery for EADs expiring in 120 days + filing statusGoogle BigQueryBigQuery
  • LogicApply auto-extension rules: covered vs action-required
  • ActionPost action-required cases to Slack with reasonSlack
  • OutputEmail next-step notice to employee via OutlookOutlook

What it does

Not every expiring Employment Authorization Document needs a panic. Many qualify for automatic extension when a timely renewal is on file. This workflow evaluates each EAD nearing expiry against auto-extension criteria, then triages: auto-covered cases are logged quietly, while cases that need a filing or are losing their extension window are escalated to HR with the reason.

When to use it

Use it when you employ EAD holders and want to cut noise — surfacing only the work-authorization cases that genuinely require action instead of alerting on every upcoming expiry. Reduces false alarms while catching the ones that matter.

How it works

  1. 1A daily schedule triggers the run.
  2. 2It queries BigQuery for EAD records expiring within 120 days plus their renewal-filing status.
  3. 3A logic step applies auto-extension rules to classify each case as auto-covered or action-required.
  4. 4Auto-covered cases are written back to BigQuery with a status note, no alert.
  5. 5Action-required cases post to the HR Slack channel with the specific reason.
  6. 6The output emails the affected employee a clear next-step notice via Outlook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect OutlookMail, calendar, contacts.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.