Who is working right now, and how many hours did the team track this week?
Jibble connects Memtro to your team's time tracking and attendance. It reads who is clocked in right now, raw clock-in and clock-out entries, and daily timesheet totals with overtime. It also reads tracked time by person or project, time off requests, timesheet approval periods, and team members with their groups. When asked and granted, it can clock someone in or out, edit or remove time entries, request and decide time off, approve or reopen timesheets, manage members, and create projects, clients, activities and holidays. Contact details, time off notes and attachments are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Jibble tool, reads what it needs, and answers with the source cited.
These tools change something in Jibble. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Jibble is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Jibble + MemtroWho is clocked in right now?
How many hours did the team track last week, including overtime?
Which time off requests are pending?
How much time went on the Website project this month?
Clock Dan Fletcher out.
Priya Sharma, operations manager at Acme Ltd, asked how many hours the team tracked last week. Memtro read the timesheet summary and gave each person's total with their overtime days. She raised the overtime with the team leads that morning.
Tom Reilly, team lead at Northwind, asked Memtro to approve Maya Okafor's pending time off request. With the action granted, Memtro approved it in Jibble, which updated her leave balance and timesheet. Jibble told Maya as the organisation has it set up.
The teams that lean on Jibble most, a question each of them asks, and what they connect beside it.
A record in Jibble is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
BambooHR
Ashby
Breathe HR
Lever
Workable
Deel
Factorial HR
Pinpoint
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMIn Jibble, open Organization settings → API Credentials and create a new secret. Only the organisation owner can create one, and the secret is shown once.
In Memtro, open Connections → Jibble and paste the API Key ID and the API Key Secret.
An administrator grants the actions by name, such as Clock a team member in, to the teams that may use them.
Ask "Who is working right now?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Jibble tools are the same everywhere.
Only when you ask, and only what it has been granted: clock a team member in; clock a team member out; edit a time entry's project, activity or note; remove (archive) a time entry; request time off for a team member; approve, reject or cancel a time off request; approve, reject or reopen a timesheet approval period; add a team member, optionally emailing an invitation; edit a team member's name, group or schedule; archive a team member, ending their access; delete a team member permanently; create a project; create a client; create an activity; add a holiday to a calendar. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API Key ID and API Key Secret. In Jibble, open Organization settings → API Credentials and create a new secret. Only the organisation owner can create one, and the secret is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
