Crewmeister

Connect AI agents to Crewmeister, a workforce management tool for time tracking, absences, and shift planning. Agents record time stamps, create and approve absences, and plan shifts so payroll and staffing data stay accurate without manual entry.

Verified 13 actions Session available

Crewmeister website ↗ Platform Documentation ↗ Capability data verified 2026-08-10

The daily attendance review starts after the last shift of the day closes

Agent runs List Stamps for yesterday and List Bookings for the same allocation dates

Agent isolates crew members whose punches never closed, so the derived booking is short or missing entirely

Agent runs List Shifts to confirm the person was actually planned to work that day before calling the gap an error

The supervisor receives each gap with the raw punches, the working time it currently produces, and the correction the agent would make

The supervisor approves each correction before Create Stamp or Delete Stamp runs, because the corrected booking is what payroll pays against

What This Integration Enables

Crewmeister serves German small and mid sized businesses where recorded working time is not a productivity metric. It is the document a payroll dispute gets settled against. The connector respects that by keeping two things separate, and understanding the split is the whole job. Stamps are the raw punches a person actually made: start work, start break, clock out. Bookings are the calculated working time derived from those punches, and bookings are what reporting and payroll read. An agent that edits a stamp is not tidying a log. It is changing what someone is paid.

FlowRunner agents work across all three of Crewmeister's areas. On time tracking they list stamps filtered by user and allocation date range, create a single punch of a given type at an exact timestamp, delete a punch by ID, and read the calculated bookings those punches produce. On absences they list records filtered by user, state, and date range, create a request over a date range with half day control at either end, change an existing absence to approved or rejected with an explanatory note, delete a record, and read remaining entitlement balances per person. On shift planning they list planned shifts by user, workplace, and start time, create a shift as either published or an unpublished draft, and delete one. List Members returns the crew roster with each person's employee ID and working day range.

Two setup facts shape how flows are built here. The connector exchanges your Crewmeister account email and password for a short lived token on each run, so the flow acts with that account's permissions and nothing narrower. Every operation is scoped to one configured Crew ID, so a business running several crews runs several connections. Both are worth knowing before an agent is given write access to time data. FlowRunner's connectors are built and verified against each vendor's official API, and Crewmeister's is the current V3 REST API.

Without FlowRunner

Corrections chased by hand A missed clock-out surfaces days later when someone questions a short paycheck

Two records, one story Raw punches live in Crewmeister and the payroll summary lives in a spreadsheet that is rebuilt every month

Entitlement checked after approval Vacation is approved first and the remaining balance is looked up afterward

With FlowRunner

Corrections surfaced the next morning Open punches are found on a daily pass while the crew member still remembers the day

One reviewed source Bookings are read straight from Crewmeister with the punches that produced them attached

Entitlement checked before approval Get Entitlement Balances runs before an absence state changes, so the balance is part of the decision

Use Case Scenarios

The Punch That Never Closed

Someone starts work at 06:00, gets pulled onto a delivery, and never clocks out. Crewmeister has the start punch and no end, so the day's booking is wrong. Each morning the agent runs List Stamps for the previous day and List Bookings for the same allocation dates, then compares each person's punches against the shift they were planned for with List Shifts. It assembles the open days into one review: the person, the punches on record, the working time those punches currently produce, and what the corrected booking would be. The supervisor decides each one. The agent then makes only the corrections that were approved. The crew member still gets asked what time they finished. What changes is that the question arrives the next morning rather than after payroll has run.

Absence Requests Answered With the Balance Attached

An employee asks for four days off in a message thread. The agent resolves them to a crew member with List Members, runs Get Entitlement Balances to read the remaining days for that absence type, and runs List Absences to check whether the same days are already covered or whether coverage is thin because two colleagues are already out. It posts the request to the manager in Slack with all three facts in one place, then runs Update Absence State on the answer with the manager's note attached. If the request is approved, Create Absence writes it over the date range with half day handling at either end. The manager is deciding with the balance in front of them rather than approving first and discovering the overdraft later.

Filling a Shift Without Publishing a Guess

Demand for the following week arrives from the scheduling side of the business. The agent reads the current plan with List Shifts, resolves who is available with List Members and List Absences, and builds the missing shifts with Create Shift left unpublished. Drafts are invisible to the crew, so nothing has been promised yet. The planner reviews the draft week, and only then does a second pass publish it. Meanwhile the approved plan is mirrored into Personio so the HR record and the shift board agree on who is where. The draft state is Crewmeister's own idea, and using it is cheaper than retracting a shift a crew member has already arranged childcare around.

Human-in-Loop Highlight

The gate sits on the retroactive punch correction, because Delete Stamp is permanent and its own description says the deletion changes the calculated working time for that day. An agent can spot a missing clock out reliably. It cannot know whether the person finished at 14:00 or worked until 18:00, and Crewmeister will not stop it from writing either. So the agent stops and asks. The message reads: "Martin Weber, Tuesday: start work 06:02, no clock out. The day is currently booked at 0 hours. The planned shift ran 06:00 to 14:30. Confirm the finish time, or leave the day open for Martin to answer?" The approver picks a time or sends it back to the employee. Only then does the agent run Create Stamp or Delete Stamp. This is human-in-the-loop placed exactly where the money boundary is: the agent finds the exceptions, and a person signs off on any edit that moves a paycheck.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

13 actions

Time Tracking

List Stamps Retrieve clock in, break, and clock out punches for the crew, filtered by user and allocation date range, with pagination. Used to review recorded working time or feed downstream reporting.
Create Stamp Record a single punch of a given type at an exact timestamp for a crew member. Used to correct a missing punch after a human has confirmed the time.
Delete Stamp Permanently delete a punch by ID. Deleting one changes the calculated working time for that day, so it belongs behind an approval.
List Bookings Retrieve the calculated working time entries derived from the punches, filtered by user and allocation date range. Used wherever payroll or reporting needs the computed number rather than the raw punches.

Absence Management

List Absences Retrieve absence records filtered by user, approval state, and date range. Used to check coverage before approving new time off.
Create Absence Create an absence request over a date range for a configured absence type, with half day control at either end and an initial approval state. Used to book leave requested through another channel.
Update Absence State Approve, reject, or otherwise change the state of an existing absence, with an optional note explaining the change. Used as the write step after a manager decides.
Delete Absence Permanently delete an absence record by ID. Used to remove an entry created in error.
Get Entitlement Balances Read remaining entitlement, such as vacation days, per person. Used to put the balance in front of the approver before the decision rather than after it.

Shift Planning

List Shifts Retrieve planned shifts filtered by user, workplace, and start time range. Used to read the current plan and find uncovered slots.
Create Shift Create a shift with start and end times, an optional workplace and break, and a choice between published and unpublished. Used to build a draft week that a planner reviews before the crew sees it.
Delete Shift Permanently delete a shift by ID. Used to remove a slot from the plan.

Members

List Members Retrieve crew members filtered by enabled status and email, including employee ID and working day range. Used to resolve a person to a crew member before any time or absence write.

Frequently Asked Questions

What can FlowRunner do with Crewmeister?

FlowRunner agents can run List Stamps, Create Stamp, and Delete Stamp in Crewmeister, plus 10 more actions.

Does connecting Crewmeister to FlowRunner require OAuth?

No. Crewmeister connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Crewmeister trigger a FlowRunner workflow automatically?

Crewmeister doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Crewmeister

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us