Skip to content
Hypamoon

For teams that run on Quinyx

Quinyx import shifts from a spreadsheet

The import tools in Quinyx take people and time tracker transactions. Shifts go into the schedule by hand, by copying or through the base schedule, and handing the shifts of someone who leaves to a colleague goes in blocks of 60 days.

How it goes today

  1. Copy a shift and paste it day by day for each employee.
  2. Drag shifts between employees when the plan changes.
  3. Hand over the shifts of someone who leaves in blocks of 60 days.
  4. Fix a wrong paste by hand, shift by shift.

How it can go

Put a season of shifts into Quinyx from one spreadsheet.

You fill a spreadsheet with date, start, end, break, employee, section and shift type. You first see a summary per week and location, and after your yes the shifts are added to the schedule in Quinyx. Rows in a period you already published wait for a second yes, and rows Quinyx does not accept come back with the reason. The shifts of someone who leaves can be set up for a colleague from a given date the same way, and the old ones removed.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Quinyx key in the portal, never in the chat.

Your request

With Hypamoon, when I share a spreadsheet of shifts with date, start, end, break, employee, section and shift type, show me a summary per week and per location first. After I agree, add the shifts to the schedule in Quinyx. Hold back rows in a period that is already published until I confirm them, and send me a list of rows Quinyx did not accept with the reason.

You find the Quinyx API key yourself under Account settings, Integrations API-keys. It stays yours.