Resources · Make integration

GIRITON Make integrationAutomate GIRITON with Make.

Can Make keep GIRITON in step with the rest of your tools? The GIRITON Make integration gives you 34 action modules for people, attendance, shifts, departments and projects. This page is for ops and HR teams: link your account, build a first scenario, then pick the right module.

Try the GIRITON integration on MakeSee the 34 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GIRITON Make integration automate?

The GIRITON Make integration links your GIRITON account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain, and all 34 GIRITON modules are actions, so they write or read GIRITON data once something else has started the scenario.

Onboarding without retyping. When a new employee appears in the app where hiring happens, Create or Update User adds the person to GIRITON and Send Account Invitation sends the invite. HR stops copying names from one screen to another.

Attendance that travels. Get Attendance Activities and Get User Activity read what GIRITON recorded, so payroll or reporting tools receive the same data the floor manager sees. In the other direction, Add Attendance To User writes an entry that was captured somewhere else.

Shift planning in sync. Get Shifts, Get Shift Plan and the shift planner updates let a team push planning changes into chat or a shared calendar, or assign people to a slot from another tool.

What the integration does not do: GIRITON has no trigger module in Make, so nothing inside GIRITON starts a scenario by itself, and there is no Make an API Call module to reach an endpoint that lacks a module. The GIRITON doc on Make is marked as AI-generated content, so check each module on a test record before you rely on it. If you also weigh n8n, the n8n vs Make comparison sets the two side by side; to learn the editor properly, see Make training, and when a run fails, Make troubleshooting helps you read the error.

Connect

How do you connect GIRITON to Make?

  1. 01

    Create a REST API token in GIRITON

    You need an active GIRITON account. In the GIRITON web app, open the Paired devices section and click + REST API token. Give the token a name you will recognize later, such as the name of your Make workspace.

  2. 02

    Reveal and copy the key

    Click the eye icon next to the new token to show it, then copy the API key displayed on screen. Keep it at hand: Make asks for it in the next step, and you paste it once for every GIRITON module.

  3. 03

    Create the connection in Make

    In your scenario, add any GIRITON module and click Create a connection. The Connection name field is optional. Paste the key, confirm, and Make stores this connection: your GIRITON account linked once, reused by every module of the app.

First scenario

Your first scenario with GIRITON

GoalWhen a new hire is added in the app your HR team already uses, Make creates the person in GIRITON and sends the account invitation.

  1. 01

    Start from the source of new hires

    On the Scenarios page, create a new scenario and click the +. Pick the app where new employees are entered, such as a form or a spreadsheet, and choose its module that returns new records.

  2. 02

    Add Create or Update User

    Click the + on the right of that first module, search for GIRITON and pick Create or Update User. Use Create a connection with the API key from the previous section.

  3. 03

    Map the employee data

    Fill the module fields by mapping the values from the first module: each new hire arrives as a bundle, one item passed from one module to the next. Make shows what it can read once the connection exists.

  4. 04

    Send the invitation

    Add Send Account Invitation after the user module and map the person that GIRITON just returned, so the invite goes to the account you created and not to an older one.

  5. 05

    Test with Run once

    Add one test employee in the source app, then click Run once. Open each module to read the bundle it received and check the new user in GIRITON before inviting real people.

  6. 06

    Schedule and switch on

    Click the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or change it, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What each GIRITON module does

GIRITON gives you 34 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

GIRITON1

Add Attendance To User

ActionIn the docs only

Writes an attendance entry onto one person's GIRITON record, so a presence captured in another tool shows up where managers already look.

When to use it
arrivals are logged by a separate form or device app and should end up on the right employee without anyone retyping them.
Watch out
the entry needs the correct person, so pick the user from a previous module rather than typing a name by hand.
GIRITON2

Create Attendance Event

ActionIn the docs only

You get a new attendance event in GIRITON, created from data that reached Make through another app. Its name points to a single event, while Add Attendance To User targets a named person.

When to use it
a check-in or check-out happens outside GIRITON and you want it logged as its own event.
Watch out
test it with Run once and open the record in GIRITON to confirm which fields it expects.
GIRITON3

Create Attendance Request

ActionIn the docs only

Files an attendance request in GIRITON on behalf of an employee, so a request typed into a form or chat reaches the approval flow without a manager copying it.

When to use it
staff ask for a correction or an absence through a tool they already use, and that ask should land in GIRITON.
Watch out
pair it with Update Attendance Request later if the request changes, instead of creating a second one.
GIRITON4

Create Or Update Projects Categories

ActionIn the docs only

Keeps your GIRITON project categories aligned with the list you maintain elsewhere: missing categories get created, existing ones get refreshed. One module covers both cases.

When to use it
your category list lives in a spreadsheet or another project tool and GIRITON should mirror it.
Watch out
run it once on a single category first, because an update overwrites what was there and Make keeps no copy of the old value.
GIRITON5

Create Shift Subscription

ActionIn the docs only

Signs someone up for a shift in GIRITON from inside a scenario, which saves a planner from adding volunteers one by one.

When to use it
people put their name down for an open slot in a form or a chat, and that choice should become a real subscription.
Watch out
the shift must already exist, so fetch it with Get Shifts in an earlier module and map its identifier.
GIRITON6

Create or Update Departments

ActionIn the docs only

Your department structure in GIRITON follows the one you keep in your HR system: this module adds departments that are missing and updates the ones already there.

When to use it
a reorganization is recorded in another tool first, and GIRITON should reflect it without manual edits.
Watch out
the doc does not say how it tells an update from a creation, so try a renamed department on a Run once before relying on it.
GIRITON7

Create or Update Project

ActionIn the docs only

A project opened in your CRM or project tool appears in GIRITON too, so the team finds it there too. If the project already exists, the module updates it instead.

When to use it
a deal is won or a job is scheduled elsewhere and the team needs the matching project in GIRITON.
Watch out
check the result after the first Run once to make sure it updated the project you meant.
GIRITON8

Create or Update User

ActionIn the docs only

Adds a person to GIRITON, or refreshes their details if they are already there, from data coming out of the previous module. This is the backbone of any onboarding scenario.

When to use it
a hire, a transfer or a change of contract details is recorded in another app first.
Watch out
creating the user does not invite them; add Send Account Invitation after it when the person needs to log in.
GIRITON9

Delete Attendance Id

ActionIn the docs only

Removes one attendance record from GIRITON, identified by its ID, which clears a duplicate or a mistaken entry without opening the web app.

When to use it
another scenario or a colleague flagged an entry as wrong and you want the fix applied automatically.
Watch out
a deletion cannot be undone from Make, so read the record with Get Attendance Activities first and test on a dummy entry.
GIRITON10

Delete Department(s)

ActionIn the docs only

Clears departments out of GIRITON once they no longer exist in your organization; the brackets in its name suggest it can take more than one at a time.

When to use it
a team is dissolved in your HR system and GIRITON should drop the matching department.
Watch out
people still attached to that department may be affected, so check with Get Users who is still in it before you delete.
GIRITON11

Delete Project Categories

ActionIn the docs only

Cleans up several GIRITON project categories in one go, which helps when a whole family of categories is retired together.

When to use it
a list of obsolete categories comes out of a spreadsheet or an earlier module and should disappear in bulk.
Watch out
compare with Delete Project Category, the single version, and keep this plural one for real batches, since one wrong list wipes several entries at once.
GIRITON12

Delete Project Category

ActionIn the docs only

Takes a single project category out of GIRITON. It is the careful choice when only one entry has to go.

When to use it
someone removes a category from your reference list and GIRITON should follow, one item per bundle.
Watch out
map the category from Get Projects Categories rather than typing it, and test with Run once on a category nobody uses, because Make cannot bring it back.
GIRITON13

Delete Project Departments

ActionIn the docs only

Detaches or removes departments linked to a project in GIRITON, going by its name, which keeps each project assigned only to the teams that still work on it.

When to use it
a department stops contributing to a project and the link should go away without touching the department itself.
Watch out
the name leaves room for doubt, so try it on a test project and check what GIRITON shows before using it on live work.
GIRITON14

Delete Shift Planers

ActionIn the docs only

Removes shift planners from GIRITON. The module keeps Make's spelling, with a single n, and that is the name you search for in the editor.

When to use it
a planning period or a planner set up for a closed site is no longer needed.
Watch out
anything planned inside it may go with it, so export what you need with Get Shift Planner in an earlier module.
GIRITON15

Get Attendance Activities

ActionIn the docs only

Pulls the attendance activities recorded in GIRITON into your scenario, ready to be sent to a payroll sheet, a report or a message.

When to use it
someone needs the attendance data outside GIRITON, for example an accountant who works in a spreadsheet.
Watch out
each activity can come out as its own bundle, and each module run on a bundle is one operation, so filter before heavy steps.
GIRITON16

Get Attendance Requests

ActionIn the docs only

Lists the attendance requests stored in GIRITON so you can route them somewhere visible, like a team channel or a manager's task list.

When to use it
requests tend to wait too long, and a scheduled scenario should surface the pending ones.
Watch out
a scheduled run reads the same requests again next time, so add a filter or a record of what was already sent.
GIRITON17

Get Departments

ActionIn the docs only

Returns the departments defined in GIRITON, which gives later modules a clean list to pick from instead of names typed by hand.

When to use it
you need to check whether a department exists before creating a user in it, or to copy the structure into another tool.
Watch out
the result may contain many items, so use a filter after it to keep only the one you need.
GIRITON18

Get Person

ActionIn the docs only

Fetches one person's details from GIRITON, so the next module works from what GIRITON holds on them, with no second lookup.

When to use it
a scenario starts from an ID or a reference and you need the full employee record before acting.
Watch out
unlike Get Users, it targets one individual, so map the right identifier from the previous module or it returns nothing useful.
GIRITON19

Get Projects

ActionIn the docs only

Reads the projects stored in GIRITON and hands them to the rest of your scenario, one bundle per project.

When to use it
a report, a dashboard or a CRM needs the same project list that your staff see in GIRITON.
Watch out
run it once and look at the output before mapping anything, so you know exactly which values Make gets back.
GIRITON20

Get Projects Categories

ActionIn the docs only

Brings back the project categories you set up in GIRITON, handy as a reference before creating or deleting one.

When to use it
another tool keeps its own category list and a scenario compares the two to spot gaps.
Watch out
it only reads data; to change the categories, follow it with Create Or Update Projects Categories or one of the delete modules.
GIRITON21

Get Shift Plan

ActionIn the docs only

Reads a shift plan from GIRITON so the schedule can be shared where the team actually looks, such as a chat channel or a shared calendar.

When to use it
a plan is published and staff should receive it without logging in.
Watch out
the doc gives no detail on what the plan contains, so test with Run once and check the bundle before building the message.
GIRITON22

Get Shift Planner

ActionIn the docs only

Returns a shift planner from GIRITON, the container your plans live in going by the module names, so a scenario can work with its content.

When to use it
before an assignment or a removal, to find the planner that the next module will change.
Watch out
planner and plan are two different modules; if the output looks wrong, try Get Shift Plan instead.
GIRITON23

Get Shift Subscriptions

ActionIn the docs only

Shows who signed up for which shifts, pulled out of GIRITON so you can count, share or check them elsewhere.

When to use it
a coordinator wants a list of subscriptions in a spreadsheet, or a reminder sent to those who signed up.
Watch out
a scheduled scenario reads the full set on each run, so keep track of what you already processed to avoid double reminders.
GIRITON24

Get Shifts

ActionIn the docs only

Collects shifts from GIRITON into the scenario, the starting point for anything that assigns, subscribes or reports on them.

When to use it
you need a shift identifier for Create Shift Subscription or the planner updates, or a list of open shifts to post.
Watch out
many shifts mean many bundles, and every later module runs once per bundle, which adds operations on your plan.
GIRITON25

Get User Activity

ActionIn the docs only

Retrieves the activity of one GIRITON user, a narrower view than Get Attendance Activities, which reads across people.

When to use it
a manager asks for one employee's record, or a scenario reacts to a single person's data.
Watch out
map the user from Get Users or Get Person first; a wrong identifier returns another person's data or nothing.
GIRITON26

Get User Profile Picture

ActionIn the docs only

Downloads a GIRITON user's profile picture into the scenario, so it can be reused on a badge, an intranet page or a directory.

When to use it
another tool shows staff photos and should use the same ones as GIRITON.
Watch out
on the Free plan, Make handles files up to 5 MB and 512 MB of data transfer, so keep an eye on volume when you copy many pictures.
GIRITON27

Get Users

ActionIn the docs only

Lists the users of your GIRITON account, the usual first step whenever a scenario must find the right person before acting.

When to use it
syncing staff into another tool, or matching an email from a form with an existing employee.
Watch out
it returns several bundles; add a filter so later modules only run for the person you need.
GIRITON28

Get Users Employed Between

ActionIn the docs only

Finds the people employed during a period you set, based on its name, which is useful for any report tied to a time window.

When to use it
payroll, a headcount report or an audit asks who was on staff between two dates.
Watch out
map the dates from the previous module or from Make's date functions instead of typing them, or the scenario keeps reading the same period.
GIRITON29

Get Users Employed On

ActionIn the docs only

Answers a simple question: who was employed on a given day. Where Get Users Employed Between covers a period, this one looks at a single date.

When to use it
a snapshot of staff on a specific day, for an incident report or a site count.
Watch out
check how GIRITON reads the date on a first Run once before trusting the list.
GIRITON30

Send Account Invitation

ActionIn the docs only

Sends a GIRITON account invitation, so a new employee gets access without an admin clicking through the web app.

When to use it
right after Create or Update User, in an onboarding scenario that starts from your hiring tool.
Watch out
test with your own address first; once the scenario is on, every new bundle triggers a real invitation.
GIRITON31

Update Attendance Request

ActionIn the docs only

Changes an attendance request that already sits in GIRITON, so a correction or a decision made elsewhere is reflected on the request itself.

When to use it
a manager approves or edits a request in a chat or a form, and GIRITON should record it.
Watch out
read the request first with Get Attendance Requests and map its identifier, since updating the wrong one overwrites someone else's data.
GIRITON32

Update Shift Planner Assing

ActionIn the docs only

Assigns people in a GIRITON shift planner from a scenario. The name keeps Make's spelling, "Assing", so search for it that way in the editor.

When to use it
assignments are decided in another tool, such as a staffing sheet, and should reach the planner directly.
Watch out
get the planner with Get Shift Planner and the person with Get Users first, then check the result in GIRITON after a Run once.
GIRITON33

Update Shift Planner Remove

ActionIn the docs only

The counterpart of the assign module: it takes a person off a GIRITON shift planner when they are no longer available.

When to use it
an absence approved elsewhere should free the slot right away in the plan.
Watch out
removing someone does not fill the gap; add a notification to the planner in the same scenario so the slot gets covered.
GIRITON34

Update Shift Subscription Subscribe

ActionIn the docs only

Updates an existing shift subscription to sign a person in, whereas Create Shift Subscription starts a new one.

When to use it
a subscription already exists for the shift and someone confirms they will take it, through a form or a chat reply.
Watch out
the difference between the two modules is not detailed in the doc, so compare both on a test shift before choosing.
Need help

Need help automating GIRITON with Make?

A person reads every message.

FAQ

GIRITON and Make: frequent questions

01Is the GIRITON Make integration free?
Yes, GIRITON is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. You still need your own GIRITON account; its subscription is set by GIRITON.
02What do you need to connect GIRITON to Make?
You need an active GIRITON account and a REST API token. In the GIRITON web app, open Paired devices, click + REST API token, name the token, click the eye icon to reveal it and copy the key. In Make, add a GIRITON module, click Create a connection, give it a name if you like and paste the key. That single connection then serves all 34 GIRITON modules in every scenario you build.
03Can GIRITON start a Make scenario in real time?
No. GIRITON has no trigger module in Make, so nothing in GIRITON can launch a scenario by itself. There are two ways to start anyway. Open the scenario with a trigger from another app, such as the tool where new hires or requests are entered, then add GIRITON modules after it. Or begin with a GIRITON read module like Get Attendance Requests and set a schedule on it: a new scenario runs every 15 minutes by default, with 1 minute as the minimum on paid plans.
04What if a GIRITON module is missing in Make?
It depends on what you need. The 34 modules cover users, attendance, shifts, departments and projects, but GIRITON has no Make an API Call module, so you cannot reach an endpoint that lacks a module from this app. Check first whether another app in your scenario can do the job. For anything beyond that, the team can look at your case with you. Keep in mind that the GIRITON doc on Make is marked as AI-generated, so test each module on sample data.
05Should you pick Make or n8n for GIRITON?
It depends on what each tool offers for GIRITON when you compare them. In Make, GIRITON has 34 action modules and no trigger, and the app is available from the Free plan. The same app often has an n8n node too, so check whether one exists and which operations it covers before deciding. Base the choice on the modules you actually need, how your scenarios will start and the tool your team already knows, rather than on general claims about either platform.
Same platform

Other docs you might need on this stack.

Browse all integrations