WARNING: Please backup your database before trying this tutorial. This will install only 5 rules and a few actions it is very light. All rules are tagged as Time Clock you can type Tags:Time Clock in search field of Rules to filter just these rules.
This requires version 5.2.23.
This tutorial will cover the integration of scheduling and time keeping suite called 7Shifts.
We will cover the time clock integration as well as the sales integration.
Here is the DB Tools Import file for the entire integration.
Step 1: Install the import file by navigating to Manage > Settings >Database Tools and choose import from file.
Step 2: Open the 7shifts script in Manage > Automation > Scripts and at the top where it says YOUR7SHIFTSAPIKEYGOESHERE insert your 7shifts API key which is located in your Company settings page in 7shifts.
Step 3: Be sure the PINCODE for SambaPOS Users matches the PINCODE for the 7shifts Employee.
Step 4: Determine your time zone and adjust the portion of the 7shifts Execute action inside the CLK Handle Clock Out and the CLK Clock User In and the 7shifts Execute rules so you add or subtract the number of seconds from 18000(USA CST Time) to match your time zone.
Yes sorry I failed to mention that. This will require 5.2.23 which is in beta test right now. I thought I had closed the topic. Sorry. I will make this beta category for now.
Sure thing
I’m looking over the rules and scripts to ensure I havent missed anything.
I got my API key which I added to the script.
The only thing I haven’t done yet is add any additional actions.
THis is because the file you shared here seems to have those rules and actions in there and when i check it, it matches what you showed in the tutorial.
I made some updates since I posted that file I may repackage it tonight and and put the updated went on there and then we can see which ones you might need and I’ll make sure that’s in it too
the 18000 seconds offset is 4 Central standard Time to their servers I can’t remember which country they were in but for me to get central standard time I had to offset it by those mini seconds I think it was 6 hours so you you can take that to to try to convert to what your offset needs to be
I actually called them and reported it as a bug because you would think that they would have the offset in their API server exactly like they do in the actual app because you choose your offset in the settings for your company and their servers handle it but for some reason they’re API doesn’t handle it that way so I was kind of frustrated and I just built offset into my script