Pro Crew Schedule Make integrationAutomate Pro Crew Schedule with Make.

Brings back one employee record so the following modules can reuse that person's details instead of you typing them again. It is an action and works on a single element.

Hands you your staff as separate bundles, one per employee, ready to be copied, counted or checked in the next modules. Being a search, it can return zero, one or many people.

Adds a new person to Pro Crew Schedule from data you map, so a hire recorded elsewhere shows up in the planner without manual entry. One bundle in, one employee created.

Changes an existing employee record with fresh data, which keeps Pro Crew Schedule in line with the tool your HR team treats as the reference. It edits one person per bundle.

Removes an employee from Pro Crew Schedule, handy for keeping the planner free of people who have left. It acts on the one person the bundle points to.

Fetches a single crew so its details can feed a message, a document or a later module in the same scenario. Handy whenever a job refers to a team and you need more than its name.

Returns your crews one bundle each, which makes a crew directory in another tool easy to rebuild from scratch. As a search, the result may hold no crew, one crew or several.

Sets up a new crew in Pro Crew Schedule from the data of an earlier module, so a team formed on paper or in a project tool becomes plannable at once.

Edits an existing crew so its record matches what happened in the field, without opening Pro Crew Schedule. Each bundle updates one crew.

Takes a crew out of Pro Crew Schedule when the team no longer exists, which keeps dropdowns and reports clean for dispatchers. It works on one crew per bundle.

Gives you every inventory item as its own bundle, a clean base for a stock report or a sync with your accounting spreadsheet. The search can come back empty, with one item or with many.

Reads one inventory record so a later module can use its details, for instance to warn someone or to fill a purchase request. It returns a single element.

Brings an inventory record up to date with data from another app, so the stock in Pro Crew Schedule matches what the warehouse really holds.

Registers a new item in Pro Crew Schedule's inventory from mapped data, so equipment bought elsewhere is available to plan with right away. One bundle gives one new record.

Clears an inventory record out of Pro Crew Schedule, which keeps crews from planning with gear that is gone. The module handles one item per bundle.

Sends out your picklists one bundle at a time, useful to print them, share them with the warehouse or archive them in a drive. The search returns zero, one or several picklists.

Opens a single picklist and passes its content on, so a crew lead can receive exactly what to load for a job in a message or a document.

Modifies an existing picklist with new data, so changes decided in a meeting sheet or a form reach the warehouse without a phone call.

Removes a picklist that no longer serves a purpose, keeping the warehouse view limited to loads that are still ahead. One bundle, one list removed.

Builds a new picklist from mapped data, so the list of material for a job exists in Pro Crew Schedule as soon as the job is decided elsewhere.

Returns your tasks as individual bundles, the starting point for a digest, a client report or a sync with a project tool. Like every search, it may find none, one or many.

Retrieves one task so its details can travel to a customer email, an invoice draft or a chat message. The result is a single element ready to map.

Erases a task from Pro Crew Schedule, so a job cancelled by the customer no longer blocks a crew's day. It deletes the one task the bundle designates.

Turns data from another app into a new job in Pro Crew Schedule, so bookings or won deals reach the planner without anyone retyping them.

Edits an existing task with new information, keeping the job in the planner in step with what the client or the office decided in another tool.

Delivers your schedules one bundle each, so you can publish them in a calendar, a sheet or a message to the field teams. The search may return nothing, a single schedule or several.

Looks up one schedule and passes its details forward, ideal for confirming a slot to a customer or a technician in the same scenario.

Adjusts an existing schedule with data from the scenario, sparing the dispatcher a manual reshuffle when a change is already recorded somewhere else.

Adds a schedule entry to Pro Crew Schedule from mapped data, so planning decided in a sheet or a booking tool lands in the app on its own.

Removes a schedule entry that no longer holds, freeing the slot in Pro Crew Schedule for another job. One bundle removes one schedule.

Shows who is assigned to which task, one bundle per link, which is the raw material for workload reports or payroll exports. The search returns zero, one or several assignments.

Changes an existing assignment, so a job can switch hands without the dispatcher reopening the planner. It edits one link between a task and a person per bundle.

Assigns an employee to a task, which is what actually puts a name on a job after Create a Task or Create an Employee. One bundle gives one assignment.

Unassigns a person from a task while leaving the task itself in place, so the job returns to the pool of work to hand out.

Reads a single assignment so the scenario knows which employee sits on which task, before notifying them or logging the pairing elsewhere.

Records an absence request in Pro Crew Schedule from mapped data, so leave asked through a form or chat reaches the planner without retyping.

Pulls one time-off record so its details can go into a confirmation email, a calendar entry or an HR file in the same run.

Hands over absences one bundle each, the basis for a shared leave calendar or a report for payroll. The search can bring back no absence, one or many.

Edits an existing absence, so a change agreed with a manager in another tool shows up in Pro Crew Schedule without a second entry.

Removes an absence from Pro Crew Schedule, so the planner no longer shows that person as away.

Keeps a time tracker in Pro Crew Schedule matching what happened in the field, without opening the app to fix it by hand. The module changes an existing tracker using data mapped from an earlier module in the scenario.

Adds a brand new time tracker to Pro Crew Schedule each time the scenario receives a bundle, which is one item passed from the previous module. Hours logged elsewhere end up in the scheduling tool with no retyping.

Pulls the full record of a single time tracker into your scenario, so the next modules can reuse its details in an email, a sheet or a report. It reads one tracker you already know.

Sends the time trackers stored in Pro Crew Schedule down the scenario, one bundle per tracker. It is the starting point for any recap or export of logged time.

Removes a time tracker from Pro Crew Schedule straight from a scenario, which keeps the timesheet clean when an entry was logged by mistake or cancelled in another system.

Shows which files are attached in your Pro Crew Schedule account, returned as separate bundles that later modules can archive, share or count.

Fetches one specific attachment so the rest of the scenario can use it, for example by forwarding it to a client or saving it next to the matching job folder.

Clears out an attachment in Pro Crew Schedule once it has served its purpose, typically after the scenario has already copied it to long term storage elsewhere.

Reaches any part of the Pro Crew Schedule API that the dedicated modules leave out, using the connection you already created, so there is no second login to set up.