--- url: "https://www.skedulo.com/platform/workflow/" type: "page" title: "Frontline Workflow Automation | Skedulo" description: "Build and automate frontline workflows across scheduling, field execution, handoffs, approvals, alerts, and operational exceptions." --- # Build and automate frontline workflows. _Workflow and Automation_ Build workflows across scheduling, mobile work and your other business systems. The Pulse Platform brings your records, business logic and automated actions together in a visual builder. [Book a Demo](https://www.skedulo.com/book-a-demo/) [Explore the Pulse Platform](https://www.skedulo.com/platform/) _Illustration: Skedulo workflow builder for Failed check follow-up, Active: Run 214 on JOB-4803 goes down the canvas, each card running in blue then checked green - Site checklist submitted, Any check failed, Request approval to Wade Brennan. As the run waits on him, his approval pops up: Approve the repair to AST-1152, JOB-4803, the photo of the isolator and the failed check, Isolator can be locked off. He presses Approve, it reads Approved 5:18 PM, and the run goes on through Repair approved to Create a follow-up job, which reads Created JOB-4871_ ## Teams using Skedulo. - Achieve3000 - American Red Cross - Connexin - ECL Group - Mainmark - Rocket Fiber _What Workflow does_ ## One workflow across teams and systems. A cancelled job may need a customer update, a change in your CRM and a follow-up task for dispatch. Build those actions into the same workflow, using the job data already in Skedulo. Use the Automation Engine to define when the process runs, which conditions it checks and how each action uses the results of earlier steps. _Illustration: Skedulo job JOB-4871, Replace isolator, AST-1152, Pending allocation, at Pioneer Health Systems, 1160 Pioneer Way, Denver: Repair, 2 hours, due Fri 15 Aug, created by the Failed check follow-up workflow from JOB-4803 at 5:18 PM. What it carried in lands section by section: the failed check, Isolator can be locked off, recorded by Gloria Benitez at 4:15 PM; the photo of the isolator; the asset, AST-1152 in the level 3 plant space; Approved by Wade Brennan at 5:18 PM; and the site access - the isolator tagged out, the plant room key with Facilities, permit PTW-2026-0884_ _WORKFLOW IN PRACTICE_ ## Approvals, exceptions, and follow-up. A missed visit or failed check can start a configured workflow. Assign follow-up tasks and route the relevant records for review as part of the process. _Approvals_ ### Approval requests with context Route forms for sign-off with the records needed to assess the request. The reviewer can check the details before making a decision. _Illustration: Skedulo web app, Wade Brennan's approvals: a new request lands at the top of his list, Approve the repair to AST-1152, from the Failed check follow-up workflow on JOB-4803, and he opens it. It carries the site checklist Gloria Benitez submitted at 5:16 PM with one failed check, Isolator can be locked off, the photo of the isolator, and what approving does - Create a follow-up job, Replace isolator, 2 hours. He presses Approve: it reads Approved by Wade Brennan 5:18 PM, the follow-up becomes JOB-4871, and the request is marked Approved_ _Exceptions_ ### Exception follow-up A configured workflow can create an assigned task when a missed visit, failed check or coverage gap is recorded. _Illustration: Skedulo web app, Tasks created by workflows: three exceptions land as tasks, each with its owner - a missed visit, No access at JOB-4826: rebook the visit, for Odette Ferreira from Missed visit follow-up; a coverage gap, JOB-4841 uncovered 2:30 to 3:30 PM, for Mark Doherty from Unavailability follow-up; and a failed check, Isolator check failed on AST-1152, for Wade Brennan from Failed check follow-up. The open count climbs from 9 to 12, above older tasks for Dana Pruitt and Mark Doherty_ _Handoffs_ ### Shared job records Office teams can review the forms, notes and status recorded in the field, along with outstanding actions. The job record provides the context for follow-up work. _Illustration: Skedulo web app, the record for JOB-4803, Quarterly site inspection at Pioneer Health Systems with Gloria Benitez, as the office sees the field's updates land: the site checklist submitted at 5:16 PM with one failed check, from Gloria Benitez in the mobile app; the status turns from In progress to Complete; her handover note to Aaron Feldman, AST-1152 is tagged out and isolated, the plant room key is with Facilities; and two outstanding actions with owners - Replace isolator, AST-1152, Aaron Feldman, JOB-4871 Fri 15 Aug; Close out permit PTW-2026-0884, Helen Pryor_ _Follow-ups_ ### Automated follow-up tasks Configure a workflow to create a follow-up task when completed work needs further attention, using the information already recorded. _Illustration: Skedulo web app, the Jobs list: Quarterly site inspection JOB-4803 shows 1 failed check, and the follow-up the Failed check follow-up workflow creates lands under it, linked - Replace isolator, AST-1152, Repair, Pending allocation, Not scheduled, 2 hours, JOB-4871. Then JOB-4803 turns from Dispatched to Complete, among the day's other jobs_ _How it works_ ## Workflow logic and controls. ### Record and event triggers Start a workflow when a record changes, a supported event occurs or a scheduled time arrives. _Illustration: Skedulo workflow trigger panel on the builder's canvas: of four ways to start - Record change, Time offset, Recurring schedule, Platform event - the pointer picks Record change, sets the record to Form response and the event to Created, and adds a filter, Only when Form is Site checklist; the trigger's title becomes Site checklist submitted_ ### Conditional logic Create different paths for different outcomes, using record values and the results of earlier actions. _Illustration: Skedulo workflow condition panel for the IF Repair approved, Continue on Then when: Request approval, Decision, is - the pointer opens the value menu and picks Approved. Tested with Run 214 the row gets a green tick, the Then path to Create a follow-up job lights, Taken in Run 214, and the Else path to Tell the dispatcher goes quiet_ ### Data and variables Use record data and action results throughout the workflow, without entering the same information at each step. _Illustration: Skedulo workflow variables panel, Variables, Run 214, Passed to the next steps: each value lands as the step that sets it runs - asset AST-1152 from the Site checklist, then decision Approved from Request approval_ ### Targeted notifications Send notifications to the people involved, with messages that include relevant details from the workflow. _Illustration: Skedulo workflow notification step, Notify the approver: the pointer sets To to Wade Brennan, the approver, and the message, Approve the repair to {asset}, previews with Run 214's value as Approve the repair to AST-1152_ ### Execution history Review each run to see which actions completed and investigate failures. _Illustration: Skedulo workflow run history for Run 214 on JOB-4803: its record lands line by line, each checked green - A check failed: Isolator, Wade Brennan approved, Created JOB-4871, Replace isolator - and the run reads Succeeded_ ### Visual workflow builder Build and adjust the process on a visual canvas, with actions and conditional branches. [Explore Extend & Customize](https://www.skedulo.com/platform/extend-customize/). _Illustration: Skedulo visual workflow builder canvas: under Create a follow-up job, the pointer presses the plus on the line to End, the step palette opens, Send message is picked, and a new step, Post in #dispatch-day, lands in its place before End_ _Triggers_ ## Event-driven and scheduled automation. Respond to changes as they happen or run a process at a planned time. Triggers can use record changes, supported platform events, recurring schedules or a time relative to a record's date. _Record Change_ ### Record changes Start when a standard or custom record is created, updated, or deleted. Filter for the object, operation, and values that matter, such as a status change or cancellation. _Illustration: Skedulo Automation Engine builder, the automation Cancelled job follow-up in draft: on the dotted canvas its trigger card is selected, the panel beside it sets it up. Object is Job; of Created, Updated and Deleted the pointer picks Updated, then adds a filter that lands chip by chip - Status changes to Cancelled - and the card renames itself from Record change to Job cancelled, Status changes to Cancelled. Under it the steps it starts: update the Salesforce work order, then if it was due within 24 hours._ _Record Time Offset_ ### Time-based triggers Start an automation a set amount of time before or after a date or time field on a record. Use it for appointment readiness checks, reminders, and credential expiry. _Illustration: Skedulo Automation Engine builder, the automation Appointment reminder in draft: the selected trigger is set up in the panel - Object Job, Date field Start time, Offset 24 hours - and the pointer picks Before of Before and After. The trigger card renames itself Before the visit, Start time, 24 hours before, and the next run lands: Thu 14 Aug, 8:00 AM, as JOB-4871 starts Fri 15 Aug at 8:00 AM. Under the trigger: text the site contact, remind the technician._ _Recurring Schedule_ ### Recurring schedules Run checks and summaries at set intervals, on a daily or weekly schedule, or with a cron expression. Set the time zone to match the operation. _Illustration: Skedulo Automation Engine builder, the automation Awaiting follow-up digest in draft: the trigger panel offers Interval, Daily, Weekly and Cron, and the pointer picks Weekly. Mon, Wed and Fri light in turn, at 7:00 AM in the America/Denver time zone, and the next three runs land - Fri 15 Aug, Mon 18 Aug and Wed 20 Aug at 7:00 AM - as the trigger card renames itself Mon, Wed and Fri, 7:00 AM, America/Denver. Under it: find assets to repair, post the digest in #dispatch-day._ _Platform Event_ ### Platform events Respond to Rules Violation events and filter their data to determine which events start the workflow. _Illustration: Skedulo Automation Engine builder, the automation Qualification check in draft: its trigger subscribes to the platform event Rules Violation, marked Beta. The pointer adds a filter on the payload that lands chip by chip - rule is Required qualifications - and the trigger card reads Required qualifications. Below, the last event received, a JSON payload for JOB-4839 and Brooke Feeney, missing Working at heights, lights its rule line: Matches the filter. Next on the canvas: create a Tempo task for Mark Doherty._ _Illustration: Skedulo Automation Engine builder, the automation Cancelled job follow-up in draft: on the dotted canvas its trigger card is selected, the panel beside it sets it up. Object is Job; of Created, Updated and Deleted the pointer picks Updated, then adds a filter that lands chip by chip - Status changes to Cancelled - and the card renames itself from Record change to Job cancelled, Status changes to Cancelled. Under it the steps it starts: update the Salesforce work order, then if it was due within 24 hours._ _Action catalog_ ## Actions built for frontline operations. Create jobs, allocate technicians, send customer messages or update a connected system. Combine actions in a workflow and use the result of one to inform the next. ### Data & Records Get records, run GraphQL queries, or create, update, and delete standard and custom records. ### Work Management Create and manage jobs, including changes to timing, resource requirements, and job locks. ### Allocations & Offers Allocate or deallocate resources, dispatch assignments, and create job or shift offers. ### Scheduling & Location Use resource and time suggestions, travel time, distance and proximity in scheduling decisions, through the available actions. ### Notifications & Integration Send SMS or push notifications, or make an HTTP request to a connected system. ### Tempo & AI Create an assigned Tempo task with the relevant work records attached. _Automation and Tempo_ ## Connect your workflows to Tempo. Create a Tempo task when a workflow needs someone's attention. Include the relevant records, priority and recipient so they can investigate without reconstructing what happened. Tasks can include job, worker, customer and other records, along with a description of the issue. Investigate-and-propose and approval-gated actions are in active development; your Skedulo team can confirm availability for your environment. ## Customer stories. ### 86% — Increase in scheduling and dispatch efficiency > “We're able to make sound business decisions that better all parties involved...” > > — [AWP Safety](https://www.skedulo.com/customers/area-wide-protective/) ### 90% — Reduction in paper-based work > “For managers, daily dashboards give a helicopter view of what we have scheduled and...” > > — [Mainmark](https://www.skedulo.com/customers/mainmark/) ### 31% — Reduction in instructor underutilization > “Skedulo worked with us to create a customized solution that is truly plug-and-play...” > > — [American Red Cross](https://www.skedulo.com/customers/american-red-cross/) _Related Pages_ ## Explore the Pulse Platform. ### Platform - [AI](https://www.skedulo.com/platform/ai/) - [Tempo](https://www.skedulo.com/product/tempo/) - [Integrations & APIs](https://www.skedulo.com/platform/integrations/) - [Public Pages](https://www.skedulo.com/platform/public-pages/) - [Extend & Customize](https://www.skedulo.com/platform/extend-customize/) ### Use Cases - [Task Management](https://www.skedulo.com/use-cases/task-management/) - [Communication & Messaging](https://www.skedulo.com/use-cases/communication-messaging/) - [Workforce Management](https://www.skedulo.com/use-cases/workforce-management/) ### Products - [Field Scheduling](https://www.skedulo.com/product/field-scheduling/) - [Shift Scheduling](https://www.skedulo.com/product/shift-scheduling/) - [Forms & Checklists](https://www.skedulo.com/product/forms-checklists/) - [Analytics](https://www.skedulo.com/product/analytics/) ## Frequently Asked Questions ### What is Skedulo Workflow and Automation? Workflow and Automation is part of the Pulse Platform. It lets you build processes that use Skedulo records, evaluate conditions and run actions across frontline work and connected systems. Those processes can also assign follow-up tasks and route information for review. ### What does the Automation Engine do within a workflow? The Automation Engine is the visual builder behind a workflow. A trigger starts the process, conditions determine the path, and actions update records, manage work, notify people, or call connected systems. ### What can start an automation? Automations can start from a record change, a time relative to a record, a recurring schedule, or a supported platform event. Current documentation includes Rules Violation events. ### What actions can an automation perform? Built-in actions cover data and records, work management, allocations and offers, scheduling and location, notifications, integration, and Tempo. See the [action reference](https://docs.skedulo.com/action-reference/guide/overview/) for the available operations and required inputs. ### Does Workflow replace manual approvals? No. People still make the decisions your process requires. Workflow can automate the routing and notifications around an approval, with the next action defined by your configuration. ### How does automation work with Tempo? An automation can create an assigned Tempo task and attach relevant work records. Approval-gated and headless agent actions are in active development; confirm availability with your Skedulo team. ### What kinds of processes does Workflow handle? Examples include responding to cancelled jobs, arranging follow-up work after an inspection, sending appointment reminders and sharing completed job details with other systems. Connections to billing or payroll use configured integrations. ### Does Workflow connect to systems outside Skedulo? Yes. HTTP actions and configured integrations connect workflows to other business systems. Each connection needs the endpoint, authentication and data required by that system. [Explore Integrations & APIs](https://www.skedulo.com/platform/integrations/). ### Can administrators see whether an automation ran? Yes. Review execution results and available step details to understand how the automation ran. ### Do automations retry failed runs? Current beta documentation does not provide automatic action retries or execution replay. Design error handling and recovery around that limitation. ### Who can manage automations? Administrators and users with the relevant permissions can view or manage automations. Test changes outside production and confirm access before activating them. ### Is the visual automation builder available to our team? Skedulo documents the Automations feature as open beta. Your administrator or Skedulo team can confirm availability and the setup needed for your environment. ## Let's look at your workflows. Bring a process you'd like to automate. We'll explore how to build it on the Pulse Platform. [Book a Demo](https://www.skedulo.com/book-a-demo/) [Explore the Pulse Platform](https://www.skedulo.com/platform/)