Resources · Make integration

Jibble Make integrationAutomate Jibble with Make.

Can Make keep Jibble in sync with the rest of your tools? The Jibble Make integration gives you 17 modules: 8 actions and 9 searches. This guide is for ops leads who track time in Jibble, and it walks you from the connection to a working first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Jibble Make integration do for you?

It links your Jibble account to Make so another tool can write to Jibble or read from it without anyone copying data by hand. You build a scenario (the automation itself, a chain of steps) out of modules, and each Jibble module either creates or updates something, or looks it up for the next step.

New team members appear in Jibble on their own. When your hiring tool records a hire, Create a Person adds them, and Update a Person keeps their record current when details change later.

Hours land where your finance team reads them. List Timesheets Daily Summary or Search Timesheets pulls tracked time, and the next module in the scenario writes it to a sheet or a reporting tool.

Client work is set up before the first hour is logged. A signed deal in your CRM can trigger Create a Client and Create a Project, with Update a Project for later edits.

One thing Make cannot do here: react to an event inside Jibble. The app has no trigger module, so every Jibble scenario starts from another app or from a schedule. The Jibble page in Make's app docs also says it was AI-generated from Jibble's documentation, so double-check any detail that matters. If you want a structured way in, the Make training covers these patterns, and Make pricing explains how runs are counted.

Many apps also have an n8n node. If you are weighing both tools, read n8n vs Make before you build.

Connect

How do you connect Jibble to Make?

  1. 01

    Generate credentials in Jibble

    In Jibble, open Organization Settings, go to the API Credentials tab and click Create New Secret. Enter the callback URI https://www.integromat.com/oauth/cb/jibble, then copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a Jibble module in Make

    Log in to Make, add any Jibble module to your scenario and click Create a connection. A connection is your Jibble account linked to Make once and reused by every Jibble module you add afterward.

  3. 03

    Paste the credentials and save

    Give the connection a clear name in the Connection name field if you like (it is optional). Paste the credentials you copied from Jibble, or follow the prompts Make displays, and save.

First scenario

Your first scenario with Jibble

GoalWhen a new hire is recorded in another app, Make creates that person in Jibble.

  1. 01

    Create a new scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. A module is one brick of the scenario: a trigger, an action or a search.

  2. 02

    Start from the app that knows the hire

    Jibble has no trigger, so the first module comes from the tool where hires are recorded, such as a form or a spreadsheet. Search for that app, pick its module and connect the account.

  3. 03

    Add Create a Person

    Click the + on the right of the first module, search for Jibble and pick Create a Person. Choose your Jibble connection, then map data from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received (a bundle is one item passed along, here one person) and check the new entry in Jibble.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between scheduled runs.

Modules

What each Jibble module does

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

Jibble1

Clock In / Clock Out

Action

In MakeClocks in with specified parameters.

Records a clock event in Jibble for someone on your team, so a shift can start or end without anyone opening the Jibble app. The time entry comes from whatever happened earlier in the scenario.

When to use it
a check-in submitted through another tool, like a site arrival form, should count as the start of a shift.
Watch out
Make runs an action once per bundle, so duplicated input clocks the same person twice. Test with Run once first.
Jibble2

Create a Client

Action

In MakeCreates a new client.

Adds a new client to Jibble, so the customer exists there the moment a deal closes somewhere else and your team can start tracking work for it.

When to use it
your CRM marks an opportunity as won and you want the account ready in Jibble before kickoff.
Watch out
the module description says nothing about duplicate checks, so put Search Clients in front of it if the same name could arrive twice.
Jibble3

Create an Activity

Action

In MakeCreates a new activity.

Creates a new activity in Jibble, so a new type of work is available to your team without an admin adding it by hand first.

When to use it
a new service line is approved in your project tool and staff need to log hours against it right away.
Watch out
run Search Activities first when you are not sure the activity already exists, or you may end up with two of them.
Jibble4

Create a Person

Action

In MakeCreates a new person/team member.

Adds a new team member to Jibble, which means onboarding no longer depends on someone remembering to invite the hire into the time tracker.

When to use it
HR confirms a start in your hiring tool or an onboarding form, and the new colleague should be able to clock in on day one.
Watch out
map only data you trust from the previous module, since this creates a real record in your organization.
Jibble5

Create a Project

Action

In MakeCreates a new project.

Opens a new project in Jibble so time can be logged against it, straight from the tool where the project was born, whether that is a signed quote or a new board.

When to use it
a client signs off on a quote and the delivery team needs a place to record their hours.
Watch out
if the project belongs to a new client, create the client in an earlier module so the order of the scenario stays logical.
Jibble6

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Lets you call any endpoint of the Jibble API from your scenario with the same connection, which covers the requests the other Jibble modules do not handle.

When to use it
you need a Jibble operation that has no dedicated module, and you have the Jibble API documentation open next to you.
Watch out
this module expects you to know the endpoint and its parameters, so it suits someone comfortable reading API docs.
Jibble7

Update a Person

Action

In MakeUpdates a person by ID.

Changes the record of an existing team member in Jibble, identified by their ID, so a promotion or a team move shows up without editing profiles one at a time.

When to use it
someone changes department in your HR system and Jibble should reflect it.
Watch out
the module needs the person's ID, so place Search People before it to find that ID from what your other app knows about the person.
Jibble8

Update a Project

Action

In MakeUpdates selected project.

Edits a project that already exists in Jibble, so a renamed engagement or a project that has moved on stays accurate in your time tracking without a manual pass.

When to use it
the project status changes in your project management tool and Jibble should follow.
Watch out
pick the right project first; Search Projects in an earlier step is the safe way to get it when several share similar names.
Jibble9

List Timesheets Daily Summary

Search

In MakeLists Timesheets daily summary for selected users.

Pulls a day-by-day summary of tracked time for the users you select, so payroll or client billing gets totals instead of raw clock events.

When to use it
a finance sheet or a reporting tool needs each person's daily hours to prepare invoices or pay.
Watch out
it returns one bundle per result, and every module after it runs for each one, which adds operations (the executions Make counts on your plan).
Jibble10

Search Activities

Search

In MakeLists activities by search criteria.

Finds the activities in Jibble that match your criteria and hands them to the next step, which is handy for checking what already exists before you create anything new.

When to use it
ahead of Create an Activity, to avoid adding a label your team already uses.
Watch out
a search can come back empty, so decide what the following modules should do when nothing matches.
Jibble11

Search Clients

Search

In MakeLists clients by search criteria.

Looks up clients in Jibble by the criteria you set, giving you their records to reuse later in the scenario without typing anything twice.

When to use it
a deal comes in from your CRM and you want to know whether that customer is already in Jibble before creating a project for them.
Watch out
a broad search may return several clients, and each one continues through the rest of the scenario.
Jibble12

Search Groups

Search

In MakeLists groups by search criteria.

Returns the groups defined in your Jibble organization that match your criteria, so the scenario can work with teams or departments rather than individuals.

When to use it
you want to report on one department, or route a newcomer to the right team based on data from another tool.
Watch out
group names typed by hand drift over time, so check the spelling Jibble actually uses with a Run once test.
Jibble13

Search Locations

Search

In MakeLists locations by search criteria.

Retrieves the locations set up in Jibble that fit your criteria, useful when your team works across several sites and each record needs the right one.

When to use it
a field team clocks in at different sites and your report groups hours by place.
Watch out
when nothing matches, the modules after it receive no bundle, so an empty result can quietly stop that branch of the scenario.
Jibble14

Search People

Search

In MakeLists people by search criteria.

Finds team members in Jibble that match what you are looking for and returns their records, including the ID other modules need to act on a specific person.

When to use it
right before Update a Person or Clock In / Clock Out, when your other app does not know the person's Jibble ID.
Watch out
two colleagues with similar names can both come back, so search on something unique whenever you can.
Jibble15

Search Projects

Search

In MakeLists projects by search criteria.

Pulls the Jibble projects that match your search, so a scenario can pick the correct one to update or report on instead of relying on a hard-coded value.

When to use it
a change in your project tool should land on the matching Jibble project through Update a Project.
Watch out
each project returned runs through the following modules, so narrow your criteria before you switch the scenario on.
Jibble16

Search Schedules

Search

In MakeLists schedules by search criteria.

Reads the work schedules stored in Jibble that meet your criteria, and passes them to another tool, such as a shared spreadsheet.

When to use it
you want to compare planned shifts with tracked hours in a spreadsheet, or share schedules with a team that lives outside Jibble.
Watch out
this module only reads schedules; nothing in the list of Jibble modules on Make creates or edits them.
Jibble17

Search Timesheets

Search

In MakeList Timesheets by search criteria.

Brings back timesheets from Jibble that match your criteria, the detailed view you reach for when a daily total is not enough and you need the entries themselves.

When to use it
a client disputes an invoice and you want the underlying time records exported to a shared file.
Watch out
detailed timesheets can mean many bundles, and every one of them costs operations in the modules that follow.
Need help

Need help automating Jibble with Make?

A person reads every message.

FAQ

Questions about Jibble and Make

01Is the Jibble Make integration free?
Yes, on the Make side. Jibble is a standard app, so it is available from the Free plan, which lets you keep 2 scenarios active, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and limits transfer to 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and allow unlimited active scenarios. You still need an active Jibble account; check Jibble's own pricing page for that subscription.
02What do you need to connect Jibble to Make?
An active Jibble account and API credentials generated inside it. In Jibble, open Organization Settings, go to API Credentials, click Create New Secret and enter the callback URI given in Make's documentation. Copy the Client ID and Client secret that appear. Then add a Jibble module in Make, click Create a connection, optionally name it, and paste those credentials. The same connection serves every Jibble module afterward, so you only do this once per account.
03Can a Jibble scenario react in real time?
No, not from Jibble itself. The Jibble app on Make has no trigger module, scheduled or instant, so nothing inside Jibble can start a scenario. You have two ways to begin anyway. Put a trigger from another app first, for example the tool where hires or deals are recorded, and add the Jibble modules after it. Or start the scenario on a schedule and open with a Jibble search, such as Search Timesheets. A new scenario runs every 15 minutes by default.
04What if the Jibble module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Jibble API with the connection you already set up, so it covers whatever the other modules leave out. You will need the Jibble API documentation to know which endpoint to call. Also keep in mind that Make's page for Jibble is marked as AI-generated from the vendor's documentation, so verify important details and contact Jibble directly if something looks off.
05Should you use Make or n8n for Jibble?
It depends on the tool your team already knows. On Make, Jibble comes with 17 modules, no trigger, and Make an API Call for anything missing, all described on this page. Many apps also have an n8n node, so check whether one exists for Jibble and what it covers before choosing. Compare the modules each tool offers for the exact tasks you need, such as creating people or exporting timesheets, and pick the one that covers them with the least workaround.