Resources · Make integration

Jitbit Make integrationAutomate Jitbit with Make.

Could your helpdesk tickets move on their own once they land in Jitbit? The Jitbit Make integration gives you 11 modules: 2 triggers, 7 actions and 2 searches. This page is for support leads who want to connect the account, build a first scenario and pick the right module.

Try the Jitbit integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Jitbit Make integration do for your helpdesk?

The Jitbit Make integration links your Jitbit helpdesk to the other tools you use, without writing code. In Make you build a scenario, which is the automation itself: a chain of modules, each one a brick that watches, creates, reads or searches something in one app. Jitbit brings 11 of those bricks.

Tickets that reach the right people. Watch Tickets picks up each new ticket, and the next module can post it to a chat channel, copy it into a spreadsheet or pass it to Update a Ticket so it gets the right details straight away.

A clean user base. When someone signs up in your CRM or form tool, Search Users checks whether they already exist in Jitbit, then Create a User or Update a User keeps a single record per person. A form tool such as the one on the 123FormBuilder Make integration page can feed that flow.

Context before a reply. Get a Ticket and Get a User pull the full record, so a later module can enrich a report or a message with the requester's details.

Know the limits before you start. Make's own documentation for Jitbit is thin and says so openly, and several user modules ask for administrator rights in Jitbit. When a listed module does not cover your case, Make an API Call reaches the rest of the Jitbit API with the same connection. Jitbit often has an n8n node too; the n8n vs Make comparison lays out the differences, and the Make training helps if you are new to the editor.

Connect

How do you connect your Jitbit account to Make?

  1. 01

    Add a Jitbit module

    In a scenario, click the +, search for Jitbit and pick any of its modules. Then click Create a connection. A connection is your Jitbit account linked to Make once, then reused by every Jitbit module you add.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when you run several helpdesks. Then follow what Make asks for: either authorize Make on the Jitbit page that opens, or paste the key Jitbit gives you into the field.

  3. 03

    Save and check

    Click Save. Make now lists the Jitbit data it can read in the module fields. If the lists stay empty, the account you connected probably lacks the rights that module needs.

First scenario

Your first scenario: open an onboarding ticket for every new user

GoalWhen a new user is created in Jitbit, Make opens a ticket so your team can welcome them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to add your first module.

  2. 02

    Add Watch Users

    Search for Jitbit, choose Watch Users and click Create a connection. Use an account with helpdesk-administrator permissions, since this trigger requires them.

  3. 03

    Add Create a Ticket

    Click the + on the right of Watch Users and pick Create a Ticket. Map the new user's details from the previous module into the ticket fields Make shows you.

  4. 04

    Test with Run once

    Create a test user in Jitbit, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one user and then one ticket.

  5. 05

    Schedule and switch on

    Open the clock on Watch Users: a new scenario checks every 15 minutes by default. Keep that or change it, then switch the scenario on so it runs without you.

Triggers

What can start a Jitbit scenario?

2 modules start a scenario when something happens in Jitbit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Jitbit as soon as it happens.

Jitbit1Watch Tickets

Watch Tickets

Scheduled trigger

In Make“Triggers when new tickets are created.”

Watch Tickets hands every newly created ticket to your scenario, so the rest of the chain can route it, log it or notify someone without anyone copying it by hand. Each ticket arrives as its own bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, 1 minute at best on a paid plan.
When to use it
as the starting point of any flow that should react to incoming support requests, such as alerting a channel for urgent topics.
Watch out
it reacts to new tickets only; a change on an existing ticket will not start the scenario.
Jitbit2Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when new users are created. Requires “helpdesk-administrator” permissions.”

Watch Users starts your scenario whenever a new user appears in Jitbit, which is the cue for onboarding, a CRM sync or a welcome message sent from another app.

How it fires
scheduled, Make checks the app on the scenario's schedule, so a new user shows up at the next check rather than the second they are created.
When to use it
when adding a person to your helpdesk should also create or tag them somewhere else.
Watch out
the connected account needs helpdesk-administrator permissions, otherwise the trigger cannot read users.
Modules

Which Jitbit modules can you add to a scenario?

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

Jitbit1

Create a Ticket

Action

In Make“Creates a new ticket.”

Create a Ticket turns something that happened elsewhere into a support request your agents will see in Jitbit: a form entry, an email, a failed payment flagged by another tool.

When to use it
when requests reach you outside the helpdesk and you want them tracked in one queue.
Watch out
add a filter before it if the source can send the same request twice, or you will get duplicates.
Jitbit2

Create a User

Action

In Make“Creates a new user. Requires “helpdesk-administrator” permissions.”

Create a User adds a person to your Jitbit helpdesk from data in another app, so customers or employees exist before they ever open a ticket.

When to use it
right after a signup, a new contract or a hire recorded in another tool.
Watch out
it requires helpdesk-administrator permissions, and running Search Users first avoids creating a second record for someone already there.
Jitbit3

Get a Ticket

Action

In Make“Returns information about selected ticket.”

Get a Ticket fetches the full details of one ticket you already know, so the following modules work from the real ticket instead of guessing.

When to use it
after a trigger or a search that only gives you a ticket reference and you need the rest.
Watch out
it reads one ticket; to find tickets by criteria, Search Tickets is the better choice.
Jitbit4

Get a User

Action

In Make“Returns information about selected user. Requires “administrator” or “technician” permissions.”

Get a User returns what Jitbit knows about one selected person, which lets you personalize a message or complete a record in another system.

When to use it
when a ticket arrives and a later module needs the requester's profile, not just a name.
Watch out
the connected account needs administrator or technician permissions, a lighter requirement than the other user modules.
Jitbit5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any part of the Jitbit API that the ready-made modules skip, while reusing the connection you already set up, so there is no new login.

When to use it
when you need an action none of the ten other modules offers.
Watch out
you write the request yourself, so keep the Jitbit API reference open; Make's own Jitbit documentation is limited.
Jitbit6

Update a Ticket

Action

In Make“Updates an existing ticket.”

Update a Ticket changes a ticket that already exists, so information gathered by your scenario lands on the request your agents are working on.

When to use it
when an event in another tool, such as a shipped order or a paid invoice, should be reflected on the matching ticket.
Watch out
you need the ticket's reference, usually from Watch Tickets or Search Tickets earlier in the chain.
Jitbit7

Update a User

Action

In Make“Updates an existing user. Requires “helpdesk-administrator” permissions.”

Update a User keeps a Jitbit profile in line with the source of truth, for instance your CRM, so agents see current details on each ticket.

When to use it
when a contact changes company, email or phone in another app and the helpdesk should follow.
Watch out
it needs helpdesk-administrator permissions, and pairing it with Search Users is the reliable way to find the right person first.
Jitbit8

Search Tickets

Search

In Make“Searches for tickets or lists them all.”

Search Tickets finds the tickets that match what you are looking for, or lists them all, and returns zero, one or many bundles for the next modules to process.

When to use it
for a report, a cleanup pass or to locate the ticket you want to update.
Watch out
every bundle it returns runs the following modules once, and each run counts as an operation on your Make plan.
Jitbit9

Search Users

Search

In Make“Searches for users or lists them all. Requires “helpdesk-administrator” permissions.”

Search Users looks up people in your helpdesk, or lists everyone, so your scenario can decide whether to create a user or update an existing one.

When to use it
just before Create a User, as a duplicate check, or to export your user base to another tool.
Watch out
it requires helpdesk-administrator permissions, and an empty result means the next module simply does not run.
Need help

Need help automating Jitbit with Make?

A person reads every message.

FAQ

Questions about the Jitbit Make integration

01Is the Jitbit Make integration free?
Yes, Jitbit is a standard app, so you can use it on Make's Free plan. That 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. Make counts usage in operations, one per module run on one bundle. Your Jitbit subscription is a separate matter.
02What do you need to connect Jitbit to Make?
A Jitbit account and a Make account are enough to start. Add any Jitbit module, click Create a connection, name it if you want, then authorize Make or paste the key Jitbit provides, and save. The real prerequisite is the role of that account: Watch Users, Create a User, Update a User and Search Users need helpdesk-administrator permissions, and Get a User needs administrator or technician rights. Make's documentation lists no other requirement, and it states that its Jitbit documentation is limited.
03Does the Jitbit trigger in Make react in real time?
No. Both Jitbit triggers, Watch Tickets and Watch Users, are scheduled: Make checks Jitbit on the scenario's schedule rather than being alerted by the app. A new scenario runs every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. Jitbit has no instant trigger in Make, so a new ticket reaches your scenario at the next check, not the moment it is created.
04What if a Jitbit module is missing in Make?
Use Make an API Call. It calls any endpoint of the Jitbit API from your scenario with the connection you already created, so you can cover actions the 11 listed modules do not offer. Plan a little extra effort: you build the request yourself, and Make says its Jitbit documentation is limited because little public information exists about the app. Keep the Jitbit API reference at hand, and check permissions first, since several user modules only work with administrator-level accounts.
05Should you use Make or n8n for Jitbit?
It depends on the tool your team already works in. On Make, Jitbit offers 11 ready modules, including 2 scheduled triggers, and Make an API Call covers the rest of the API with the same connection. Jitbit often has an n8n node as well, so both routes can work. Compare the modules each platform lists for Jitbit against the flow you have in mind, and pick the editor your team will actually maintain. There is no ranking to give between the two on this app.
Same platform

Other docs you might need on this stack.

Browse all integrations