The problem
Badges, directories, and networking apps all lean on registrant photos. Swoogo’s registration form collects one photo at a time, from one registrant, uploading their own. That’s fine when people upload their own photos as they register. It falls apart the moment an event organizer already has a batch of photos on hand — sourced from a company directory, a prior event, or an ID system — and needs them attached to the right registrant records before badges print. Doing that through the standard form would mean opening each registrant one at a time.
The approach / solution
- Built a Node.js script that reads a batch of registrant records and their matching photo files.
- The script writes each photo directly to the correct registrant’s profile-picture field using Swoogo’s own image API.
- Runs once, as a batch job ahead of an event — no manual per-registrant editing needed.
Outcome / result
Staff hand off a batch of photos and get a full set of registrant records updated in one run. What used to be hundreds of individual edits became one script execution.
Why it matters for enterprise event-tech
Data operations like this rarely show up in a sales deck, but they’re what event staff actually spend their week on before a show. A platform is only as fast as its slowest manual task, and turning a hundreds-of-clicks job into one script run is a real time saving on the ground, not a theoretical one.
