Resources · Make integration

JOBka Make integrationAutomate JOBka with Make.

Can Make keep your JOBka staff records in step with the rest of your tools? The JOBka Make integration gives you 16 modules: 13 actions and 3 searches covering employees, groups and QR codes. This page shows how to link your account, build a first scenario and pick the right module.

Try the JOBka integration on Make See the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the JOBka Make integration do for you?

The JOBka Make integration lets a Make scenario, the automation you build as a chain of modules, work on your JOBka account without code. Each module is one brick: here, an action that creates, edits or deletes an employee or a group, or a search that lists employees, groups or QR codes.

Onboarding without retyping. When a new person appears in another app you already use, Create an Employee adds them to JOBka and Add Employee to a Group places them in the right team. One scenario replaces two manual entries.

Clean exits. When someone leaves, Remove Employee from a Group takes them out of a team, and Delete an Employee removes the record once you are sure. Put the delete last, after a check.

A report other tools can read. List of Employees, List of Groups and List of QR Codes return every matching item as separate bundles, so a later module can write each one to a sheet or a message.

Make's own documentation for JOBka is limited: it states that there is not enough public information about the app to describe it fully. Test each module with Run once before you trust it. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what a plan includes. To learn the editor properly, see the Make training.

Connect

How do you connect JOBka to Make?

01
Add a JOBka module
In a scenario, click the +, search for JOBka and pick any module. Then click Create a connection. A connection is your JOBka account linked to Make once, and every JOBka module reuses it afterwards.
02
Name it and authorize
Give the connection a name if you like, for example the company it belongs to. Then either approve Make on the JOBka page that opens, or paste the key JOBka gives you, depending on what the window asks for.
03
Save and check
Click Save. Make goes back to the module, and the connection now appears in its dropdown. From there Make can fill in the lists it is able to read, such as your groups, so you pick instead of typing.

First scenario

Your first scenario with JOBka

GoalWhen a new hire appears in another app, Make creates the employee in JOBka and adds them to a group.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. JOBka has no trigger, so the first module comes from the app where your new hires are recorded.
02
Add Create an Employee
Click the + to the right of the first module, search for JOBka and choose Create an Employee. Pick your connection, then map the person's details from the previous module.
03
Place them in a group
Add Add Employee to a Group next. Map the employee returned by the previous module, then choose the group from the list Make reads from your account.
04
Test with Run once
Click Run once. Make runs the scenario one time and shows the bundles each module received. Open them to confirm the employee landed in the right group.
05
Schedule and switch on
Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan. Then switch the scenario on.

Modules

Every JOBka module, explained

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

JOBka1

Add Employee to a Group

ActionIn the docs only

Puts an existing employee into one of your groups, so team membership follows from an event elsewhere instead of a manual click.

When to use it

right after Create an Employee in an onboarding flow, or when a role changes in the tool that owns your org chart.

Watch out

the employee and the group must both exist first; map their identifiers from earlier modules rather than typing names.

JOBka2

Create a Group

ActionIn the docs only

Adds a new group to JOBka, giving you a fresh container for a team, a site or a project that just started.

When to use it

when a project or location is created in another app and you want JOBka to mirror it without anyone setting it up by hand.

Watch out

run List of Groups first if the scenario may fire twice, otherwise you can end up with two groups of the same name.

JOBka3

Create an Employee

ActionIn the docs only

Creates a new employee record in JOBka from data another module passes along, which is the heart of any onboarding scenario.

When to use it

a signed contract, a completed form or a new row in a hiring sheet should turn into a JOBka employee.

Watch out

Make keeps no memory of who already exists, so check with List of Employees before creating when the same person could come through again.

JOBka4

Delete a Group

ActionIn the docs only

Removes a group from JOBka for good, which keeps your list tidy when a team or a project is closed.

When to use it

as the final step of a project shutdown, once members have been moved with Remove Employee from a Group.

Watch out

a delete cannot be undone from Make; add a filter or a check before this module and test it on a dummy group.

JOBka5

Delete an Employee

ActionIn the docs only

Erases an employee record from JOBka, the last move when someone has left and their record is no longer needed.

When to use it

at the end of an offboarding flow, after group removals and any export you want to keep.

Watch out

there is no undo from the scenario, so map the identifier from a search result instead of a typed value, and keep Run once tests on a test record.

JOBka6

Edit a Group

ActionIn the docs only

Updates an existing group, so a renamed team or site in another tool shows up under its new details in JOBka as well.

When to use it

a department changes its name in your HR or project tool and you want JOBka to follow.

Watch out

you need the group's identifier; get it from List of Groups or Group Detail earlier in the scenario.

JOBka7

Edit an Employee

ActionIn the docs only

Changes the details of an employee who already exists, keeping JOBka aligned when information moves on elsewhere.

When to use it

a person's details change in the tool that owns them and JOBka should follow.

Watch out

Make's documentation does not say how blank values are handled, so map only what really changed and check the record after Run once.

JOBka8

Employee Detail

ActionIn the docs only

Fetches one employee's record, giving the following modules the data they need without you copying it by hand.

When to use it

you have an employee identifier from a search or another app and need that person's full record before sending a message or updating a sheet.

Watch out

it reads a single record; to go through several people, start from List of Employees.

JOBka9

Group Detail

ActionIn the docs only

Reads one group and hands its information to the rest of the scenario, useful when a later step depends on what that group contains.

When to use it

before Edit a Group, to see the current state, or to include group data in a report.

Watch out

it needs a group identifier; List of Groups is the simplest way to get one.

JOBka10

Import Employees

ActionIn the docs only

Brings several employees into JOBka in one go, which suits a first setup or a batch coming from another system.

When to use it

moving your staff list from a spreadsheet or another tool, rather than calling Create an Employee once per person.

Watch out

Make's documentation gives no detail on the expected input; try it with a small batch and Run once before sending the full list.

JOBka11

List of Employees

SearchIn the docs only

Returns your employees as separate bundles, one per person, so each can be handled by the next modules.

When to use it

to check whether someone already exists before creating them, or to build a staff export in a sheet.

Watch out

a search can return zero, one or many bundles, and each bundle that flows on counts operations in the modules after it.

JOBka12

List of Groups

SearchIn the docs only

Lists the groups in your account, each as its own bundle, which gives you identifiers to reuse in later modules.

When to use it

before Create a Group to avoid a duplicate, or to feed a group identifier into Edit a Group.

Watch out

if it returns nothing, the modules that follow do not run; plan for that case when a group may be missing.

JOBka13

List of QR Codes

SearchIn the docs only

Pulls the QR codes stored in JOBka as individual bundles, so you can log them, share them or check them elsewhere.

When to use it

when you keep a register of your codes in a sheet or need to pass them to another app.

Watch out

Make's documentation does not say what a QR code record holds; run it once and read the bundles before mapping anything.

JOBka14

Make an API Call

ActionIn the docs only

Calls any endpoint of the JOBka API with the same connection, covering what the other modules do not offer.

When to use it

you need an operation that has no ready-made module in the list above.

Watch out

Make's documentation on JOBka is limited, so you will need the JOBka API reference itself to know which endpoint and parameters to send.

JOBka15

QR Code Detail

ActionIn the docs only

Retrieves a single QR code and exposes its data to the rest of the scenario, handy when you already know which code you are after.

When to use it

after List of QR Codes, or with an identifier from another app, to read one code before acting on it.

Watch out

the fields returned are not documented; check the output bundle with Run once before building on it.

JOBka16

Remove Employee from a Group

ActionIn the docs only

Takes an employee out of a group while keeping their record, which is what you want when someone changes team rather than leaves.

When to use it

a transfer is recorded in another tool, followed by Add Employee to a Group for the new team.

Watch out

the employee remains in JOBka; use Delete an Employee only if the record itself should go.

Need help

Need help automating JOBka with Make?

A person reads every message.

FAQ

Frequently asked questions

01Is the JOBka Make integration free?

Yes, JOBka is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Every module execution on one bundle counts as an operation against your plan. Paid plans such as Core, Pro and Teams lower the interval to 1 minute and remove the cap on active scenarios.

02What is needed to connect JOBka to Make?

A JOBka account and a Make account. Make's documentation lists no prerequisites and no official connection steps for JOBka, so the generic flow applies: add a JOBka module, click Create a connection, optionally name it, approve Make on the JOBka page or paste the key JOBka provides, then click Save. The connection is created once and every JOBka module in your scenarios reuses it. If the window asks for a key, look for it in your JOBka account.

03Does JOBka trigger Make scenarios in real time?

No, JOBka has no trigger module in Make, neither scheduled nor instant. To start a scenario anyway, use a trigger from another app, for example the tool where new hires are recorded, and place the JOBka actions after it. You can also run a scenario on Make's schedule: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. Paid plans can run as often as every minute.

04What if a JOBka module is missing in Make?

Use Make an API Call. It sends a request to any endpoint of the JOBka API through the same connection, so you can cover what the 16 listed modules do not. Keep in mind that Make's documentation for JOBka is limited: it says there is not enough public information to describe the app in full. You will need the JOBka API reference to know which endpoint to call, and testing each request with Run once is the safest path.

05Is Make or n8n better suited to JOBka?

It depends on your criteria rather than on a winner. On Make, JOBka offers 16 modules covering employees, groups and QR codes, plus Make an API Call for anything else, and it runs on the Free plan. Many apps also have an n8n node, but that is not confirmed for JOBka here, so check the n8n node list before choosing. Compare how each tool fits your team and the other apps your scenarios will touch.

Add a JOBka module

Name it and authorize

Save and check

Create the scenario

Add Create an Employee

Place them in a group

Test with Run once

Schedule and switch on

Need help automating JOBka with Make?