Events that start a workflow
In the workflow editor, What starts it offers these. Each one is explained in Start a Workflow.
- A form is submitted: Someone fills in a form and clicks Submit.
- A web request: Another system, like an online store, a booking site, or a form builder, sends a request to the workflow’s web address.
- On a schedule: At a time of day, or every few hours between two times, every day or on the days you choose.
- A shift starts or ends: For each shift, at its start or end, or a set amount of time before or after. It can check whether the person checked in, was late, or didn’t show up. Uses shifts from Schedule, sent through the Skidle API, or brought in from Square.
- Someone arrives or leaves: When someone checks in or out. Only when Checking in and out is turned on, or when people clock in with Square.
- A shift request: When someone asks for cover or a swap, or when someone takes a shift. A workflow can approve or deny it. Only when Schedule is turned on.
- Messages left unread: When someone has a chat message they haven’t read for a set amount of time. Only when Team chat is turned on.
- A store event: When catalog items or stock counts change, or an order is placed or updated. Only when Catalog, Inventory, or Orders is turned on in the Square settings.
Events sent to webhooks (API)
A webhook is an address Skidle calls when something happens. Choose the events when you create the webhook in Account under Developers. Each delivery is described in the API reference. See API and Webhooks to get started.
| Event | When it’s sent | Available |
|---|---|---|
task.created | A task was created | Always |
task.updated | A task’s title, values, priority, due date, or assignee changed | Always |
task.moved | A task moved to another stage or board | Always |
task.deleted | A task was deleted | Always |
comment.created | Someone commented on a task | Always |
event.occurred | One of your own events happened, like a delivery | Always |
person.created | Someone was added to the account | Always |
person.updated | Someone’s name, roles, status, or permissions changed | Always |
person.removed | Someone was removed from the account | Always |
person.invited | An invitation was sent | Always |
shift.published | A shift was published, or a published shift changed | For shifts made in Schedule, sent through the API, or brought in from Square. |
shift.cancelled | A published shift was canceled | For shifts made in Schedule, sent through the API, or brought in from Square. |
presence.clocked_in | Someone checked in | Only when Checking in and out is turned on, or when people clock in with Square. |
presence.clocked_out | Someone checked out | Only when Checking in and out is turned on, or when people clock in with Square. |
presence.break_started | Someone started a break | Only when Checking in and out is turned on, or when people clock in with Square. |
presence.break_ended | Someone ended a break | Only when Checking in and out is turned on, or when people clock in with Square. |
shift_request.created | Someone asked for cover, a swap, or an open shift | Only when Schedule is turned on. |
shift_request.accepted | Someone took a shift that someone else asked about | Only when Schedule is turned on. |
shift_request.decided | A shift request was approved or denied | Only when Schedule is turned on. |
time_off.requested | Someone asked for time off | Only when Schedule is turned on. |
time_off.decided | A time-off request was approved or denied | Only when Schedule is turned on. |
ping | A test, sent from Developers or the API | Always |
Events that need a feature turned on
Not every account uses every feature. An admin turns these on in Settings. Until a feature is on, its events never happen, and the editor doesn’t offer its triggers.
- Schedule: the A shift request trigger,
shift_request.created,shift_request.accepted,shift_request.decided,time_off.requested,time_off.decided. - Checking in and out: the Someone arrives or leaves trigger,
presence.clocked_in,presence.clocked_out,presence.break_started,presence.break_ended. - Team chat: the Messages left unread trigger.
Events from integrations
Integrations are optional. Every event above works without one. When you connect one, it can also be where these events come from. For example, when your team clocks in with Square, each Square timecard becomes a check-in in Skidle. It starts the same Someone arrives or leaves workflows and sends the same presence.clocked_in event as a check-in made in Skidle. Each part has one home: if Square keeps the schedule or the time clock, you manage it in Square, and Skidle shows it. Each integration’s page in Integrations lists the events it feeds.