Release Notes

Release Notes: 2026-05-29

See imported Rippling employees in Abloomify, run syncs on demand, and keep GitHub knowledge syncs steady

May 29, 2026

Abloomify Team

2 min read

Abloomify release notes cover image for May 29 2026

Imported Rippling people are now visible, plus steadier GitHub knowledge syncs

This release brings imported Rippling employees into view inside Abloomify, lets admins run an employee sync whenever they need to, and keeps GitHub-sourced knowledge syncs steady through brief access interruptions. Teams that connected Rippling can now confirm their people and org-chart context before relying on the data. No action is required for teams that do not use Rippling or GitHub knowledge syncs.

What's new

See imported Rippling people in Abloomify

After connecting Rippling, the synced employees appear directly in the integration settings, so admins can confirm the import looks right.
  • A synced employees table lists imported people inside the Rippling integration settings
  • Each person carries org-chart context: department, division, team, and office
  • Role context comes through too, including manager, role, career family, career track, and career level
  • Teams can confirm employee data imported correctly before relying on it in Abloomify

Run a Rippling employee sync on demand

Admins can pull the latest Rippling people into Abloomify when they choose, with a connection that stays secure from setup onward.
  • A manual employee sync brings the latest Rippling people into Abloomify on demand
  • Reconnecting or reauthorizing Rippling completes cleanly
  • The connection and employee sync run through a secure setup

More reliable GitHub knowledge syncs

GitHub-sourced knowledge syncs now recover from brief access interruptions instead of failing.
  • GitHub knowledge syncs that hit a brief access interruption now recover on their own
  • Valid syncs that previously stalled on a passing error now complete
  • When access is genuinely changed or revoked, the sync still reports the issue clearly

Who benefits

  • Admins connecting Rippling: a synced employees table to confirm imported people before relying on the data
  • People and HR operations teams: org-chart context, including department, team, manager, and career level, visible in Abloomify
  • IT and security reviewers: Rippling connection and employee sync run through a secure setup
  • Teams using GitHub knowledge: fewer failed knowledge syncs when access is briefly interrupted

Try it

  • Open Integrations and select Rippling to review the synced employees table after setup
  • Trigger a manual employee sync from the Rippling integration settings to pull the latest people
  • Confirm org-chart fields like department, team, and manager imported as expected
  • Reconnect Rippling from Integrations if a prior setup attempt needs reauthorization
Share this article
← Back to Release Notes
Abloomify Team
Abloomify Team
Editorial Team

The collective voice of Abloomify's product, engineering, and customer success teams sharing insights from the frontlines of AI-powered workforce management.