OTHER

Route VIP and speaker badges for sign-off before printing

When a VIP or speaker registration lands in Airtable, generates a proof badge and emails it to the event lead via Outlook for approval.

CategoryOther
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew registration row in AirtableAirtableAirtable
  • LogicContinue only for Speaker or VIP tickets
  • ActionGenerate proof badge imageImage generation
  • ActionEmail proof to event lead via OutlookOutlook
  • OutputSet row to Awaiting Approval to hold print queueAirtableAirtable

What it does

Adds a human checkpoint for the badges that matter most. For VIP and speaker tickets, it generates a proof badge and sends it as an Outlook email to the event lead, with the attendee's details, so titles and name spellings get a real review before anything prints.

When to use it

Use it when a wrong speaker title or misspelled executive name is a reputational problem. Pair it with a general-attendee badge flow that prints automatically; this flow handles only the high-stakes subset that warrants eyes-on approval.

How it works

  1. 1A new Airtable registration row triggers the run.
  2. 2A branch checks the ticket type; only Speaker and VIP rows continue.
  3. 3A proof badge image is generated from the attendee's name, title, and company.
  4. 4The proof is emailed via Outlook to the event lead with an Approve or Fix instruction and the attendee record link.
  5. 5The Airtable row is set to Awaiting Approval so it stays out of the auto-print queue until the lead flips it to Approved.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  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.