Log inStart trial

7Shifts and Keeping Integration

Demonstration of how apps are integrated in WEXTL workflow builder [4]

Build hr workflows between 7Shifts and Keeping on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

Integration guide
  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about 7Shifts and Keeping

Detailed info you need to know about 7Shifts and Keeping integrations in WEXTL. Explore which modules apps support and how you connect them.

  • 7Shifts

    • HR
    • 1 trigger
    • 20 searches
    • 26 actions

    Restaurant employee scheduling, time tracking, and team management. [5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

    Time tracking software for logging hours against clients, projects and tasks. [6]

How to connect 7Shifts to Keeping

Set up your 7Shifts and Keeping integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.

  1. STEP 1

    Connect 7Shifts and Keeping

    Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.

  2. STEP 2

    Build a workflow

    Paste selected 7Shifts and Keeping nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.

  3. STEP 3

    Map your data

    Choose which fields need to sync between 7Shifts and Keeping. Use filters or leverage a JS custom code step in between — everything is on the canvas.

How does the integration between 7Shifts and Keeping work in WEXTL?

WEXTL exposes actions and triggers for 7Shifts and Keeping that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.

7Shifts triggersKeeping actions

7Shifts modules

  • Clear a Task Clears a task by marking it as completed or deleted.
  • Complete a Task Marks a task as completed.
  • Create a Location Creates a new location in the system.
  • Create a Receipt Creates a new receipt.
  • Create a Shift Creates a new shift.
  • Create a Time Punch Creates a new time punch.
  • Create a Time-Off Entry Creates a new time-off entry.
  • Create a User Creates a new user.
  • Create an Employment Record Creates a new employment record.
  • Create Availability Creates a new availability.
  • Deactivate a User Deactivates a user in the system.
  • Delete a Location Deletes a location.
  • Delete a Shift Deletes a shift from the schedule.
  • Delete a Time Punch Deletes a time punch from the system.
  • Delete a Time-Off Entry Deletes a time-off entry.
  • Delete an Availability Deletes an availability from the system.
  • Delete an Employment Record Deletes an employment record.
  • Get a Location Retrieves a location.
  • Get a Receipt Retrieves a receipt.
  • Get a Shift Retrieves a shift.
  • Get a Task List Retrieves a task list.
  • Get a Time Off Entry Retrieves a time-off entry.
  • Get a Time Punch Retrieves a time punch.
  • Get a User Retrieves a user.
  • Get an Availability Retrieves an availability.
  • Get Availabilities Retrieves a list of availabilities.
  • Get Daily Sales and Labor Retrieves daily sales and labor data.
  • Get Daily Stats Retrieves daily statistics.
  • Get Employment Records Retrieves a list of employment records.
  • Get Locations Retrieves a list of locations.
  • Get Receipts Retrieves a list of receipts.
  • Get Shifts Retrieves a list of shifts.
  • Get Task Lists Retrieves a list of task lists.
  • Get Time Off Retrieves a list of time-off entries.
  • Get Time Punches Retrieves a list of time punches.
  • Get Users Retrieves a list of users.
  • Get Worked Hours and Wages Retrieves worked hours and wages.
  • Make an API Call Performs an arbitrary authorized API call.
  • Update a Location Updates a location with new details or coordinates.
  • Update a Receipt Updates a receipt's information in the service.
  • Update a Shift Updates a shift for a specific employee or job.
  • Update a Time Punch Updates a time punch for a specific user or entry.
  • Update a User Updates a user.
  • Update an Employment Record Updates an employment record in the system.
  • Update Availability Updates an availability entry in the system.
  • Update Time Off Updates a time-off entry.
  • Watch Events Triggers when a 7shifts webhook event is received.

Keeping modules

  • Archive a Project Sets a project's state to archived.
  • Archive a Task Sets a task's state to archived.
  • Create a Client Creates a new client.
  • Create a Project Creates a new project.
  • Create a Task Creates a new task.
  • Create an Entry Creates a new time entry.
  • Delete a Client Permanently deletes a client.
  • Delete a Project Permanently deletes a project.
  • Delete a Task Permanently deletes a task.
  • Delete an Entry Permanently deletes a time entry.
  • Get a Client Retrieves a client by ID.
  • Get a Project Retrieves a project by ID.
  • Get a Task Retrieves a task by ID.
  • Get a User Retrieves a single user of the organisation.
  • Get an Entry Retrieves a single time entry.
  • Get Current User Retrieves the organisation user that belongs to the connection in use.
  • List Clients Lists the clients in the organisation.
  • List Organizations Lists all your currently active organisations.
  • List Projects Lists the projects in the organisation.
  • List Tasks Lists the tasks in the organisation.
  • List Timesheet Entries Lists time entries in the organisation.
  • List Users Lists the users in the organisation.
  • Make an API Call Sends a custom authorized request to the Keeping API.
  • Restore a Project Sets an archived project's state back to active.
  • Restore a Task Sets an archived task's state back to active.
  • Resume an Entry Resumes a stopped time entry.
  • Stop an Entry Stops a running time entry.
  • Update a Client Updates a client by ID.
  • Update a Project Updates a project by ID.
  • Update a Task Updates an existing task.
  • Update an Entry Modifies an existing time entry.
  • Watch Clients Triggers when a new client is added to an organisation.
  • Watch Organizations Triggers when a new organisation becomes available.
  • Watch Projects Triggers when a new project is added to an organisation.
  • Watch Tasks Triggers when a new task is added to an organisation.
  • Watch Timesheet Entries Triggers when a new time entry is added to an organisation.
  • Watch Users Triggers when a new user is added to an organisation.

Explore alternative integrations

There are other apps [9] supported by WEXTL that can be paired with 7Shifts and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate 7Shifts and Keeping on WEXTL®

Claim your 3-day trial to build 7Shifts with Keeping integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting 7Shifts and Keeping.

How do I connect 7Shifts and Keeping?

Connect your 7Shifts and Keeping accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]

What can I automate between 7Shifts and Keeping?

Example: when 7Shifts's "Watch Events" fires, WEXTL can "Archive a Project" in Keeping. 7Shifts has 1 trigger (including Watch Events); Keeping has 31 actions (including Archive a Project, Archive a Task, and Create a Client). Add filters and transforms between steps when you need them. [1]

Can 7Shifts trigger actions in Keeping, and Keeping in 7Shifts?

Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]

Do I need to write code to integrate 7Shifts and Keeping?

No. 7Shifts-to-Keeping automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]

Does 7Shifts integrate with Keeping in real time?

Yes. Trigger-based automations start the moment 7Shifts (or Keeping) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]

How long does it take to set up a 7Shifts + Keeping integration?

A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect 7Shifts with Keeping?

You can build your 7Shifts + Keeping automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]

References

List of sources used to gather information about the 7Shifts and Keeping integration.

  1. 7Shifts and Keeping integration source code, module specs and credentials implementation.
  2. Our 7Shifts and Keeping integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for 7Shifts and Keeping — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. 7Shifts integration information
  6. Keeping integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted 7Shifts and Keeping integration page documentation. Used sources, AI's role, and how the team validates the result.

Explore 7Shifts and Keeping, or get started