NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro

HiBob + Memtro

Who's who, who reports to whom, and who's out today.

Connect HiBob and Memtro knows your org: every person's role, department, site and manager, team sizes, who is on leave, and who joined or left recently. Read-only through a service user; only directory-level fields are requested and salary or personal data never are.

What you can do with HiBob in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right HiBob tool, reads what it needs, and answers with the source cited.

01

New manager orientation

Ask for a department: Memtro returns headcount, the managers and their reports, so the new lead can learn the org before the first 1:1.

02

Planning around absences

Ask who is out during a release week: Memtro lists the people and leave dates so owners can be reassigned in time.

  • Find people by name, email, title, department, site or manager
  • Manager chains, direct reports and team trees
  • Departments and sites with headcounts
  • Who is out of office in any date range
  • Starters, leavers and an individual's role changes

Ask it like this

Questions people ask once HiBob is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›Who does Priya report to and who is on her team?
  • ›How big is Engineering by site?
  • ›Who is out next week?
  • ›Who started in the last month?

Where it fits

Teams that get the most from HiBob in Memtro, with the rest of their stack attached.

Better together

A record in HiBob is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in People and HR

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01In HiBob create a service user under Settings → Integrations → Automation → Service users
  2. 02Add it to a permission group that can view People's work data and Time off
  3. 03In Memtro choose HiBob and enter the service user ID and token
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The HiBob tools are the same everywhere.

Set it up as an MCP server →Clients and agents →

Questions

Can Memtro change anything in HiBob?
Not yet. Today every HiBob tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
Who can use a HiBob connection?
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.
Does Memtro store my HiBob data?
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. An hourly sync anchors recently changed HiBob records into memory as entities.
How do I connect HiBob?
API key. In HiBob create a service user under Settings → Integrations → Automation → Service users.

Connect HiBob in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.