Jibble Zapier integrationAutomate Jibble with Zapier.
The Jibble Zapier integration gives you 17 triggers, 15 actions and 11 searches. A clock-in, a break, a new person or a new project can start the automation, and it can clock someone in, log manual hours or open a client, on the free plan too.
Verified Trustpilot reviews · AI, automation & growth agency
What the Jibble Zapier integration actually does
It links your Jibble time-tracking account to the other tools you use, without code. On Zapier, an automation is called a Zap: one starting event, then one or more steps that run every time that event happens. Jibble can be the event, the step, or both.
Three things people build first. An attendance feed: New Clock-In, New Clock-Out and Go on Break push each punch into a sheet or a chat channel, so the floor manager sees who is on site without opening Jibble. A tidy onboarding: a hire created elsewhere becomes a Jibble member through Create Person and Send Invite, invitation included. A client-to-project bridge: when your CRM signs a client, Create Client and Create Project set up the matching entries so hours land in the right place from day one.
What Zapier does not do here: none of the 17 triggers is instant. Every one is checked on a timer, so a clock-in shows up downstream after the next check, not the second it happens. There is also no delete action, so removing a person or a project stays a manual job in Jibble. Timesheets come out as a CSV link through a search, not as a file pushed to you.
If you are weighing tools, the same app is covered on our Jibble Make integration page, and the n8n vs Zapier comparison is there to weigh the two tools side by side.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are, once, in plain English.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens in Jibble or elsewhere.
- Trigger
- The event that starts the Zap, such as a clock-out in Jibble. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like clocking a person in.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant one is reported by the app the moment it happens. Jibble's are all polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something already in Jibble, a person or a project, so later steps can reuse what it found.
- Connection
- Your Jibble account linked to Zapier once, then reused by every step of every Zap that touches Jibble.
What a Jibble Zap really costs
Jibble is not a premium app, so it runs on the free plan. The bill comes from tasks, not from the app.
- Free plan tasks100 per month
- Zaps on the free planUnlimited, two steps each
- Premium appNo
- Trigger checksFree, never billed
The trigger never costs a task, and neither do the checks Zapier runs to find new punches. Each action that succeeds counts once, so a Zap with two actions costs twice as much per run; one that fails is not counted. The catch on the free plan: Zaps of two steps only, one trigger and one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. Many Jibble flows want a Find Person before Clock In, so budget for that.
Connect your Jibble account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Jibble account first, plus access to any team data you do not own and want the Zap to read or change.
- 02
Pick Jibble and confirm
Type Jibble in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Jibble side, where the actual sign-in happens.
- 03
Sign in and grant access
Log in to Jibble in that tab and allow Zapier to use the account. Back in Zapier, the connection is listed and every Jibble step can reuse it without asking again.
Your first Jibble Zap, step by step
GoalEvery new Jibble client with a real name gets its own project, without anyone retyping it.
- 01
Create the Zap
Start a new Zap. Pick Jibble as the starting app and New Client as the event, then choose your Jibble connection. It is the first of three steps: build, test, publish.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent clients of the account, so you map fields on a real record instead of a blank sample.
- 03
Add the filter
From the plus icon, add Filter: field Name, rule that it exists. This third step makes the Zap multi-step, so it needs a paid plan.
- 04
Add the action
Add Jibble again, pick Create Project and drop the client name from step one into the required Name field. Test it once and check the project in Jibble.
- 05
Publish
Click Publish to switch the Zap on. From now on each new client is picked up at the next check, and only the project creation counts as a task.
Jibble triggers on Zapier
17 events start a Zap when something happens in Jibble. Zapier checks for them at the interval your plan allows.
New Clock-Out
Polling triggerIn Zapier“Triggers when someone clocks-out.”
Starts the Zap each time somebody ends a shift in Jibble, carrying who it was so the next step can log the departure, notify a lead or close a timesheet line somewhere else.
New Activity
Polling triggerIn Zapier“Triggers when a new activity is created.”
Fires when someone adds a new activity to the Jibble account, the labels people pick when they clock in to say what they are working on. The Zap receives its name and can copy it elsewhere.
New Client
Polling triggerIn Zapier“Triggers when a new client is created.”
Reacts the first time a client record appears in Jibble, so whatever you do with clients (billing, CRM, folders) starts from the place where hours are tracked.
New Clock-In
Polling triggerIn Zapier“Triggers when someone clocks-in.”
Picks up every start of shift recorded in Jibble, and hands that punch to the following step.
New Group
Polling triggerIn Zapier“Triggers when a new group is created.”
Signals a freshly created group in Jibble. Groups usually mirror teams, sites or departments, so this is the moment to set up the matching structure in your other tools.
New Location
Polling triggerIn Zapier“Triggers when a new location is created.”
Watches the list of work locations in Jibble and starts the Zap when a new location appears in it at the next check, with its name ready for the next step.
New Person
Polling triggerIn Zapier“Triggers when a new member is added.”
Catches each member added to the Jibble organization. The new person's details travel to the next step, which makes it a natural start for any onboarding chain.
New Project
Polling triggerIn Zapier“Triggers when a new project is created.”
Notices each project created in Jibble at the next check and passes it along, so time-tracking and project tools stop drifting apart.
New TimeEntry Record
Polling triggerIn Zapier“Triggers when someone clocks-in, clocks-out or go on break.”
The broadest of the attendance triggers: one Zap run per punch, whether it is a clock-in, a clock-out or a break. Handy when you want a full log instead of three separate Zaps.
New or Update Client
Polling triggerIn Zapier“Triggers when a new client is created or updated.”
Fires on two moments: when a client is created and when an existing one is edited. The Zap gets the current version of the record each time.
New or Update Group
Polling triggerIn Zapier“Triggers when a new group is created or updated.”
Follows the life of every group: its creation, then each change made to it in Jibble, such as a new name after a reorganization.
New or Update Manual Time Entry
Polling triggerIn Zapier“Triggered when manual time entry is added for member”
Reacts when hours are added by hand to a member's timesheet, on top of the punched time. These manual corrections are exactly what managers want to see.
New or Update Location
Polling triggerIn Zapier“Triggers when a new location is created or updated.”
Covers both new work locations and edits to existing ones, so a changed address or a new name reaches your other tools without a manual update.
New or Update Person
Polling triggerIn Zapier“Triggers when a new member is added or updated.”
Tracks team members from the day they join through every later change to their profile in Jibble, delivering the up-to-date record each time.
Go on Break
Polling triggerIn Zapier“Triggers when someone is on break.”
Spots the moment a team member switches to a break in Jibble. It is the only trigger dedicated to pauses, which makes break tracking possible without the full punch log.
New or Update Activity
Polling triggerIn Zapier“Triggers when an activity is created or updated.”
Runs both when an activity is born in Jibble and whenever someone edits it, so the label list in your other apps never falls behind.
New or Update Project
Polling triggerIn Zapier“Triggers when a project is created or updated.”
Fires when a project is created and again each time it is changed, delivering the project as it stands now. Use it instead of New Project when edits matter.
Jibble actions on Zapier
Jibble gives you 15 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Clock In
ActionIn Zapier“Clocks the person in.”
Starts a shift for a team member straight from another tool, as if they had punched in Jibble themselves.
Clock Out
ActionIn Zapier“Clocks the person out.”
Ends the running shift of a given member, closing their time for the day without them opening the app.
Create Activity
ActionIn Zapier“Creates an Activity.”
Adds an activity label to Jibble, the tag people choose to say what they are working on. Only the name is needed.
Create Client
ActionIn Zapier“Creates a Client”
Opens a client record in Jibble from data held elsewhere, typically your CRM or a signed quote, with just a name required.
Create Group
ActionIn Zapier“Creates a Group.”
Builds a new group in the Jibble organization, the container for a team, a site or a department.
Create Location
ActionIn Zapier“Creates a Location.”
Registers a work location in Jibble. It needs a name and an address, and Jibble accepts the address in any form because it only displays it.
Create Manual Time Entry
ActionIn Zapier“Adds manual time entry (e.g. 1 hour) on top of tracked time using clock ins and outs”
Adds hours and minutes by hand to a member's day, on top of what their punches already recorded.
Create Person
ActionIn Zapier“Creates a new person.”
Adds a member to Jibble with only a full name, without sending them anything.
Create Project
ActionIn Zapier“Creates a Project.”
Sets up a project in Jibble so time can be logged against it, from a name alone.
Create Person and Send Invite
ActionIn Zapier“Creates new Team member and sends him invite.”
Goes one step further than Create Person: the new member is added and receives an invitation to join the Jibble account.
Update Activity
ActionIn Zapier“Updates an Activity.”
Changes an existing activity in Jibble, for example to correct its name when the source label changes.
Update Client
ActionIn Zapier“Updates a Client.”
Edits a client already in Jibble so its details follow what changed in your CRM or billing tool.
Update Group
ActionIn Zapier“Updates a Group.”
Modifies an existing Jibble group, the way you would by hand after a team reshuffle.
Update Location
ActionIn Zapier“Updates a Location.”
Brings an existing work location up to date in Jibble, such as a corrected address or name.
Update Project
ActionIn Zapier“Updates a Project.”
Revises a Jibble project, keeping its time history while its details change.
Jibble searches on Zapier
11 search steps look for data that already exists in Jibble, so a later step can use it.
Searches sit at the bottom of the action list in the editor, under SEARCH. They look up a person, a project or a report so later steps can use it. Nine of them also come in a find-or-create version: same search, one box ticked, not an extra operation. Each search is a step, so the Zap becomes multi-step.
Find Activity
SearchFind or createIn Zapier“Finds an Activity by name.”
Looks up an activity by its name, so a later step can update it or attach time to it.
Find Client
SearchFind or createIn Zapier“Finds a Client in Jibble by name.”
Retrieves a Jibble client from its name, the cheapest way to avoid duplicate clients.
Find Group
SearchFind or createIn Zapier“Finds a Group in your organization by name.”
Finds a group of your organization when all you have is its name, as typed in another app.
Find Group by Group Id
SearchFind or createIn Zapier“Finds a Group by Group Id.”
Fetches a group from its Jibble identifier rather than its name, which is safer when names change.
Find Location
SearchFind or createIn Zapier“Finds a Location by name.”
Searches the work locations by name, to hand the matching location to the next step.
Find Location by Location Id
SearchFind or createIn Zapier“Finds Location by Location Id.”
Returns one location from its Location Id, with no doubt about which site is meant.
Find Person
SearchFind or createIn Zapier“Finds a Person in your organization by email.”
Locates a team member from their email address, the usual bridge between Jibble and HR or email tools.
Find Person by Person Id
SearchFind or createIn Zapier“Finds a Person by Person Id.”
Pulls a member's record from their Person Id, the identifier Create Manual Time Entry also requires.
Find Project
SearchFind or createIn Zapier“Finds a Project by name.”
Finds a project by name and returns it with its Project ID, the value Update Project insists on.
Find Timesheets Report as a CSV
SearchIn Zapier“Finds a Timesheets Report as a CSV Url.”
Produces a timesheets report for a date range and hands back a link to the CSV file, ready to be sent or stored.
Find Timesheets Summary
SearchIn Zapier“Finds Timesheets Summary.”
Returns a summary of the timesheets over a period, rather than a file, so its totals can be mapped into another step.
The three settings every search exposes
- Successful if no search results are found?Left as is, a search that finds nothing stops the Zap and skips what depends on it. Switched on, the Zap carries on with empty values.
- Create X if it doesn't exist yet?Ticking it turns the search into find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
- If multiple search results are found?Three ways out when several records match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a Jibble Zap breaks
Zapier attaches no help article to Jibble, so the risks below are the general ones, applied to attendance data.
Most failures come from timing, loops and missing values. If a case below is not enough, our Zapier troubleshooting page walks through the fixes.
Old punches are never picked up
A Zap only reacts to what happens after it is published. Clock-ins from last week stay where they are; moving that backlog is a separate job.The Zap triggers itself
Writing back into the same Jibble record your trigger watches, say updating a client from New or Update Client, restarts the Zap again and again and eats tasks fast.A bulk import gets held back
Importing many people or projects at once can return a huge batch on the next check, and Zapier's flood protection may hold it back.Duplicates are filtered for you
Zapier remembers what it has already seen on a polling trigger, so the same punch does not start the Zap twice. A duplicate usually means two Zaps.The search finds no one
With default settings, a Find Person that finds nothing stops the Zap and the clock-in after it is skipped. Check the email used on both sides.A date in the wrong format
Manual time entries and timesheet searches want dates written yyyy-mm-dd. A date in another shape from the source app makes the step fail.
Need help automating Jibble with Zapier?
A person reads every message.



