Overview
What are actions?
Actions are reusable, discrete operations that the Skedulo platform can execute on your behalf: creating and updating records, sending notifications, making HTTP requests, managing jobs, and more. Each action accepts a defined set of inputs (arguments) and returns a structured response you can inspect or use in subsequent steps.
Actions can be used in these places:
| Where | Status |
|---|---|
| Automations | Available |
| API | Coming soon |
| Connected functions | Coming soon |
| Horizon components | Coming soon |
Beta feature
All actions are currently in beta. Learn about the automations beta.Action categories
Actions are grouped into categories based on what they do.
| Category | Description |
|---|---|
| Data | Create, read, update, and delete records of any core or custom object. Includes a GraphQL Query action for advanced read operations. |
| Work Management | Create and manage jobs, including creating resource requirements, duplicating jobs, moving job times, and canceling or locking jobs. |
| Related Data | Retrieve data related to a job or resource, such as the contacts for a job or the jobs assigned to a resource. |
| Allocations | Allocate and deallocate resources to jobs, and dispatch allocated resources. |
| Offers | Create job and shift offers, and send offer notifications to resources. |
| Scheduling | Suggest optimal resources and time slots, geocode addresses, calculate travel times, and locate resources. |
| Notifications | Send push notifications and SMS messages to resources. |
| Integration | Make HTTP requests to external systems. |
| Utility | Utility actions for testing and debugging, such as Echo. |
How actions work in automations
Each action step you add to an automation has:
- Request: Inputs the action needs to run (some required, some optional).
- Response: The output the action returns after it runs.
See Response format for full details on the standard output structure shared by all actions.
Further reading
Feedback
Was this page helpful?