How a Hospitality Staffing Firm Automated Travel and Contract Tracking with Bullhorn + Zapier
A hospitality staffing firm used Bullhorn and Zapier to turn booking, extension, and signed-agreement emails into self-updating tracking for ~100 consultants.
TL;DR: A small hospitality staffing firm with about 100 consultants on assignment at any given time replaced a travel coordinator's inbox-and-spreadsheet routine with Zapier automations that read booking and signature emails, match each one to the right placement in Bullhorn, and file, track, and alert without anyone copying data by hand.
The firm places temporary staff (front desk agents, managers, and other hotel roles) with hotels across the US. Each placement comes with paperwork and logistics: a hotel services agreement, a consultant agreement (1099 or W-2), travel to the property, and frequent extensions or date changes once the consultant is on site.
The internal team is small: three recruiters, a travel coordinator, accounting, and a principal who runs operations, roughly a dozen Bullhorn users in total. At any point about 100 consultants are out on assignment, and the travel tracker routinely holds more than 120 flights across active trips.
Their stack was already reasonable: Bullhorn as the ATS/CRM, a corporate travel booking platform, Adobe Sign for agreements, Microsoft 365 (Outlook, OneDrive, Excel), and a Zapier account with some existing workflows. Location matters here for one reason: they place people in many states, and a few states (California and Oregon among them) have final-pay rules that change what has to happen when an assignment ends.
The problem
Every important event in the business arrived as an email. Booking confirmations, extension approvals, date-change requests, signed agreements, résumés, end-of-assignment notices. None of those emails updated anything on their own.
So people did it by hand. The travel coordinator read each booking confirmation and typed flight details into a spreadsheet, created calendar events per flight leg, saved the PDFs into folders, and moved finished assignments to a "completed" tab. Signed agreements had to be downloaded from email and attached to the right placement in Bullhorn. When a date changed, the instruction was to highlight the row red and fix it manually.
The principal put it plainly on an early call: the emails "keep coming in," and "someone has to manually grab them or put them in Bullhorn."
The cost wasn't one big failure. It was a steady stream of small ones: a traveler missing from the calendar, an agreement not attached to the placement, an extension that never made it to the tracker, and a travel coordinator re-keying data that already existed in an email.
What they'd already tried
They weren't starting from zero. The principal had built several Zaps himself, including one that turned booking emails into calendar events and an early attempt at scraping hotel job boards for sales leads. They worked some of the time. Bullhorn's built-in Zapier actions were limited, authentication tokens expired mid-run, and anything involving name matching (a traveler's legal name on a ticket versus their name in the CRM) broke quietly. He came in wanting help with "improvements and fixes," which is a common place to land: the automations exist, but nobody fully trusts them.
What we built with Bullhorn and Zapier
A Connex consultant with Bullhorn experience worked with the principal in recurring working sessions over about 15 months, building in small, testable pieces rather than one big launch.
1. Booking emails become structured travel records. Zapier parses each booking confirmation (including multi-leg trips in a single email), extracts trip ID, traveler, flights, and dates, and writes them to the travel tracker. It creates one calendar event per flight leg, converts airport-local times to Central time, renames ticket PDFs with trip ID, traveler, and departure date, and files them in a per-consultant folder with a link back from the tracker. Cancellation emails are filtered out so they don't create ghost trips.
2. Every record is matched to the right placement first. Before anything is created, the automation looks the traveler up in Bullhorn, first by a dedicated legal/travel-name field added for this purpose, then by first and last name. If there's no confident match, it stops and emails the team a specific error instead of guessing. Lookups were later tightened to return only active placements, so a consultant with dozens of past placements doesn't match the wrong one.
3. Agreements generate, file, and track themselves. Hotel and consultant agreements (1099, W-2, direct hire) are generated from Bullhorn data into templates, including amenity terms such as prorated weekly meal allowances. As Adobe Sign emails arrive, each step (sent, consultant signed, client signed, fully executed) is timestamped in an agreement summary, and the executed PDF is attached to the placement in Bullhorn. If a company isn't active, or a document is missing a placement ID, the workflow stops and alerts the recruiter who owns that placement.
4. Extensions, date changes, and endings keep everything current. Extension and change-request emails update the tracker and the consultant's "date available" in Bullhorn. When a scheduled end date passes, the assignment is flagged and archived. Terminations in final-pay states trigger an immediate alert to payroll.
5. One place to look. The separate flight, train, driving, and home-based spreadsheets were consolidated into a single Microsoft List in SharePoint, with filtered views per role, color-coding by transportation type, and direct links into Bullhorn placements and booking folders.
Guardrails throughout. A custom Bullhorn connection replaced the built-in Zapier app to stop the token-expiry failures. Error emails name the exact record and reason. High-volume flows were rebuilt to protect the task budget: the agreement-timestamp flow, which the principal calculated at 25 Zapier tasks per agreement (five timestamps at five tasks each), moved into Power Automate, which the firm's Microsoft 365 licenses already covered for standard-connector flows once IT switched it on (as of October 2026, check Microsoft's current licensing terms).
The results
~100 active consultants tracked from email, not by hand. Booking, extension, and agreement emails update the tracker, the calendar, the folders, and Bullhorn automatically.
One line per person currently out. The consolidated SharePoint list shows each active placement once, with trip IDs, flight details, and links, instead of three spreadsheets and a "completed" tab maintained by hand.
Mismatches surface instead of hiding. Name and placement mismatches now generate a specific alert instead of a silently wrong calendar event or a missing attachment.
Compliance-sensitive endings are caught. Terminations in final-pay states reach payroll as soon as the email arrives.
Automation costs under control. At peak the account was running roughly 300 to 500 Zapier tasks a day against a 10,000-task monthly plan. Moving the heaviest flow into Power Automate and batching a 3,481-contact cleanup at 750 records a day kept the work inside that budget.
No labor-hours estimate is given here: the sessions never captured a reliable before-time per booking or agreement, and we'd rather show real scale than invent a figure. Figures above are from the client's own systems and working sessions.
Client voice
After the travel workflows were rebuilt, the firm's principal checked in with the person who uses them all day, then relayed it on the next call: the travel coordinator "says it's working and hasn't had any issues." Over the engagement he kept booking follow-up sessions and steadily handed over more of the back office: introduction emails to billing contacts and timesheet approvers, orientation emails for new placements, and résumé intake into Bullhorn.
FAQ
Will this work if we already use Bullhorn and Zapier?
Yes. This firm kept Bullhorn as the system of record and kept Zapier for event-driven work. The fix was making those Zaps reliable: a stable Bullhorn connection, match-before-write logic, and clear error alerts.
What if our team lives in Microsoft 365?
That's where this ended up. Trackers moved from Excel into SharePoint Lists, and some high-volume flows moved into Power Automate because the license was already paid for.
How fast was the first measurable win?
The first agreement-upload and travel-tracker workflows were running within the first few sessions. The rest was built incrementally, one workflow at a time, with the team using each piece as it landed.
What access did it need?
A Bullhorn API user, access to the shared inboxes that receive booking and signature emails, and edit access to the relevant OneDrive/SharePoint locations. The client stayed in control of every account.
Running a staffing desk out of your inbox?
If booking confirmations, signed contracts, and extension emails are still being copied into spreadsheets and your ATS by hand, that's fixable without replacing your stack. Book a call with Connex and we'll map which emails should be doing the work for you.
How a branded-merchandise company used Make and Pipedrive to automate self-serve store onboarding: next-step emails, 24-hour reminders and a 48-hour drip.
How a 3-tech equipment service business turned AI-answered calls into a technician dispatch board in Airtable that sorts calls, routes them, and closes jobs.
A small nonprofit connected fundraiser, school, and sponsor sign-up forms to Salesforce with Zapier, merged duplicate workflows, and added error alerts.
