Integrations

Plays well with your stack.

Formclock is one app for the whole team, so you need fewer integrations. We're honest about what's live today versus what's on the roadmap.

Live today

Three, and they all work now.

Everything under this heading ships in the product you can sign up for in the next four minutes. None of it is a beta, a waitlist, or a partner conversation.

Payroll CSV export

Hours, overtime and cost as a clean CSV your payroll provider imports.

Kiosk (any tablet)

Turn any tablet into a shared PIN clock, with optional verification photos.

Calendar feeds (iCal)

Subscribe to your shift schedule from any calendar app that reads iCal.
Not built yet

And six we haven't built.

These are on the roadmap and nothing more. They are listed because you will ask, and finding out after you have moved your team across is worse than reading it here.

  • Toast POS

    Planned: staff to sales data from Toast.

    Roadmap

  • Square POS

    Planned: staff to sales data from Square.

    Roadmap

  • Clover POS

    Planned: staff to sales data from Clover.

    Roadmap

  • Gusto payroll

    Planned: send approved timesheets straight to Gusto.

    Roadmap

  • ADP payroll

    Planned: send approved timesheets straight to ADP.

    Roadmap

  • Slack notifications

    Planned: schedule and coverage alerts in Slack.

    Roadmap

Need a specific integration? Tell us on the contact page and we'll weigh it in.

Why this list is short, and what that should tell you

Three integrations are live and six are marked roadmap. That is a small number and we would rather show it than pad it, because the alternative is the wall of logos that this category is known for, where a third of the marks are a partnership announcement and another third are a webhook somebody wired once and never maintained.

The honest read is this: if your decision depends on a direct connection to a specific payroll provider or POS today, we are not the right choice today, and a comparison page that told you otherwise would be wasting your evaluation time. If your decision depends on scheduling and time tracking being right, and payroll being a clean export, the list is long enough.

CSV export is the integration that never breaks

Direct integrations are better when they work. They also break when a vendor changes an API, deprecates a field, or rotates an auth scheme, and they break silently in the direction of wrong numbers rather than obvious errors.

A payroll CSV has none of that failure mode. Hours, overtime and cost come out in a file you can open and read before anybody is paid from it, which means a mistake is visible to a human at the one moment a human is looking. Every payroll provider we know of imports one. It is unglamorous, and for the part of the process where being wrong costs the most, it is the option we would still choose after the direct connectors exist.

How to tell a real integration from a logo on a page

Four questions separate the two, and they work on any vendor including this one. What exactly moves, in which direction, and how often? Is it live or is it announced? What happens when it fails, and would you find out from the tool or from payroll? And who maintains it, the vendor or a third-party connector platform you would also be paying for?

A useful integrations page answers all four without you asking. That is why the rows here carry a status rather than only a name, and why the roadmap ones say planned in the text rather than sitting in the same grid looking identical to the working ones. Hold every vendor to that, and hold this page to it too. If a row here ever reads as more finished than it is, it is a bug worth reporting.

See it with your own schedule

Set up a workspace, add your team, and build a week. It takes about ten minutes and costs nothing.

Start free