














































Beekeeper is a mobile-first communication and workflow platform for frontline employees who work without a desk or corporate email. An ETH Zurich spin-off founded in 2012, it joined LumApps Group in July 2025 and is now part of LumApps. Hotels, factories and retailers use it to reach staff through Streams, posts and chats, run digital checklists, forms and incident reports, assign tasks, and handle shift swaps and approvals. Through Makini's Unified API, an industrial software product can bring its alerts and records to the people on the floor, where the connection supports it. A predictive maintenance tool that has raised a work order in the plant's CMMS can post a notice to the Stream for that line, so operators see it on their phones. An EHS product reads users and groups to match each site's crews with its own location records. An OEM service portal checks a site's groups before sharing maintenance instructions. A Beekeeper user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. Beekeeper grants API access through bot accounts that an administrator creates in the Dashboard; a bot has normal member permissions unless Admin Permissions is turned on, so agree its groups with the customer. LumApps is merging the two products in phases, so confirm the customer's tenant before rollout.
Have any questions? We’re here to help You
Yes, Beekeeper joined LumApps Group in July 2025 and is now part of LumApps. LumApps says Beekeeper customers keep their contract, pricing, login and dedicated support contacts, and that a unified product experience will roll out in phases over 12 to 18 months while the current Beekeeper experience stays intact. Search results may show either brand.
Yes, Beekeeper has a public API, and its help center now points to the documentation on the LumApps developer portal at api.lumapps.com. Integrations such as Zapier work through a bot account and its Access Key. With Makini, the customer authorizes access in Makini Link, so the key never passes through the vendor's product.
In the Beekeeper desktop app, open the Dashboard with the speedometer icon, choose Extensions, then Bot Accounts, and create the bot. Copy its Access Key from the overview list. Turn on Admin Permissions only if the bot must add, edit or remove Streams, Posts, Comments, Groups and Users, and turn on Visible to Users to list it in the User Directory.
Beekeeper offers user sync with ADP, Microsoft Azure Active Directory, SAP SuccessFactors, Workday and UKG Ready, so employee profiles are updated from the HR system as people join and leave. For an integration this usually makes the HR system, not Beekeeper, the source of truth for users, so read the Beekeeper directory instead of creating users from outside.
Makini's Beekeeper page describes read and write access to Beekeeper's core records but does not list data objects, so confirm with Makini what the connection exposes. In Beekeeper those records include users, groups, Streams, posts and comments. Maintenance and EHS products usually need the user directory, the groups that reflect sites or shifts, and the Streams where notices reach workers.
A Beekeeper post appears in the mobile feed of everyone in its Stream once it is published, so a mapping error is seen by a whole shift instead of staying in a database. Read users and groups first, match them to your own site and crew records, and check the result with the customer. Then post to one test Stream, where the connection supports writes.
