Scheduled employee sync from HiBob
Employees, work emails, start dates, anniversaries and location flow from HiBob to FLYP via secure data sync on a regular schedule. The program runs against up-to-date data — no manual exports.
FLYP works with HiBob, kits trigger themselves.
HiBob is the source of truth for new hires, start dates and work anniversaries. FLYP receives the relevant data via secure data sync and runs the kit logistics — design, address collection, global production, delivery and reporting.
- Scheduled HiBob sync
- Event-driven
- Global delivery
See it in action
HiBob · ConnectedAuto-sync
- New hire synced from HiBob
- Welcome kit funded · sized from profile
- Delivered before day one ✓
- Spend logged back to one dashboard
No CSV exports · No manual triggers
HiBob runs the people events. FLYP runs the merch.
HiBob already knows who joined, when, and where they sit. FLYP plugs into that and turns lifecycle events into merch moments — without your People team chasing addresses or maintaining a sidecar gifting spreadsheet.
Hire-date triggers welcome kits
When a new hire's start date hits in HiBob, FLYP fires the welcome kit. Address collection is self-serve via a personalized link, so personal data never has to live inside HiBob.
Work-anniversary triggers recognition gifts
Anniversaries in HiBob drive milestone gifts — 1, 3, 5 and 10-year tiers configurable per program. Employees get something they'll keep on their desk, not a generic plaque.
Self-serve address collection
Personal shipping addresses live in FLYP, not HiBob. Each employee gets a branded, secure link to confirm address and size — keeping personal data out of the HR system of record.
What People teams ask before connecting HiBob to FLYP.
How does FLYP integrate with HiBob?
FLYP works with HiBob via secure data sync. HiBob is the source of truth for new hires, start dates, work anniversaries and location — FLYP receives the relevant data on a regular schedule and runs the kit logistics. Exact integration depth varies per customer; talk to sales for current scope.
What HiBob data does FLYP read?
Employee name, work email, start date, work anniversary date, country/region (for shipping), and optionally department or role for segmentation. Sensitive HR data (compensation, performance, reviews) never enters FLYP. Personal shipping addresses are collected self-serve via secure links sent to the employee.
When does HiBob trigger a kit?
The most common triggers are new-hire start date (welcome kit), work anniversary (recognition gift), and milestone events like promotions. FLYP can also fire one-off campaigns against a HiBob-synced employee list — e.g. an annual swag drop or an event kit for a specific team.
How are addresses collected from HiBob employees?
FLYP sends each employee a secure, personalized self-serve link to confirm their shipping address and pick size/fit. This means personal addresses live in FLYP, not HiBob, and you don't have to keep them in sync. The link is branded for your company and pre-fills name and email from the HiBob sync.
Can we manually override a HiBob-triggered kit?
Yes. The company admin portal lets program owners pause a trigger, swap the kit for a specific hire, add a one-off recipient who isn't in HiBob, or hold kits for batch shipping. The HiBob sync gives you a default workflow; the portal gives you the override.
Is HiBob employee data secure inside FLYP?
Yes. All data sync runs encrypted (TLS in transit, encrypted at rest), with DPAs available for EU/UK customers. SSO is supported for the company admin portal. Employee data is only stored as long as needed to run the active programs.
