Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the 7shifts connector page.How 7shifts webhooks are set up
There is nothing to configure in 7shifts and no URL to copy. StackOne registers one company webhook in 7shifts for each event you enable, pointing at its own receiver, and removes them again when the account is disconnected.
- No callback URL to paste, and no verification step to complete.
- Webhooks are registered against the 7shifts company whose Company ID this connection uses.
- Only the events you enable in StackOne are registered in 7shifts and delivered.
- You can review the registered webhooks in 7shifts under Company settings > Developer Tools > Webhooks.
Before you connect
Check the 7shifts company is on a plan that allows webhooks and that the token can manage them.
- The company must be on a Premium/Gourmet plan or higher.
- Create the Access Token as a company Admin — webhooks and the data they deliver follow that admin’s permissions.
- Keep the Company ID on this connection correct. 7shifts stamps every delivery with that company id, and StackOne uses it to match inbound events to this account.
Available webhook events
The following 7shifts events can be enabled. Only events selected in StackOne are registered in 7shifts and delivered — 7shifts will not send events you have not subscribed to.
User events
Events on employee records.
- User Created (
user.created) — Fired when a user is created, naming the locations, departments and roles they were assigned - User Modified (
user.modified) — Fired when a user record changes, including when an inactive user is made active again - User Deactivated (
user.deactivated) — Fired when a user is deactivated, naming both the deactivated user and whoever deactivated them - User Reactivated (
user.reactivated) — Fired when a previously deactivated user is reactivated
Time punch events
Events on time clock entries. Each payload is the full time punch record, including its breaks.
- Time Punch Created (
time_punch.created) — Fired when a time punch is created - Time Punch Edited (
time_punch.edited) — Fired when the punch record itself changes, such as clock in or out, role or tips. Adding, editing or deleting a break does not fire this event - Time Punch Deleted (
time_punch.deleted) — Fired when a time punch is deleted; the payload carries the record with its deleted flag set
Scheduling and payroll events
Events on published schedules and closed payroll periods.
- Schedule Published (
schedule.published) — Fired when a schedule is published, naming the location, the departments covered and the published date range - Payroll Period Closed (
payroll_period.closed) — Fired once a payroll period is closed for every location in the company
Location, department and role events
Events on the company’s organization structure.
- Location Created (
location.created) — Fired when a location is created - Location Modified (
location.modified) — Fired when a location’s details change - Location Deleted (
location.deleted) — Fired when a location is deleted - Department Created (
department.created) — Fired when a department is created - Department Modified (
department.modified) — Fired when a department is modified - Department Deleted (
department.deleted) — Fired when a department is deleted - Role Created (
role.created) — Fired when a role is created - Role Modified (
role.modified) — Fired when a role’s details change - Role Deleted (
role.deleted) — Fired when a role is deleted