Skip to content
Hypamoon

For teams that run on Nmbrs

Nmbrs calendar: team leave that stays up to date

Nmbrs exports leave to a calendar file, one kind at a time, for this year and next. A change in a leave request means a new export, and each import becomes a separate calendar.

How it goes today

  1. Export leave from the Nmbrs calendar tab as a file.
  2. Import it into the shared calendar.
  3. Export again when leave changes or is cancelled.
  4. Combine the separate calendars by hand.

How it can go

Team leave in your own calendar, kept up to date.

You get one calendar link per team to subscribe to in your own calendar app. It shows approved leave from Nmbrs, and sick leave as away without a reason if you want that. The calendar is refreshed each day, so a new or cancelled request shows up without another export.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Nmbrs works with a sign-in instead of a key: you sign in to Nmbrs once to give access, never in the chat.

Your request

With Hypamoon, make a calendar link per department that we can subscribe to. Show approved leave from Nmbrs with the employee's name and dates, and sick leave as away without a reason. Refresh it each day so new and cancelled leave shows up.

For Nmbrs in the Netherlands, you register your own app in the Nmbrs Payroll developer portal on the Starter subscription, which needs no approval, and sign in to Nmbrs once to give it access. It stays yours.