Ask Connecteam who is on shift tomorrow, and which tasks are still open.
Connect Connecteam with an API key and Memtro reads the people in the account with job title, department and manager, shifts in a date window with who is assigned, and task boards with each task's status, assignee and due date. Pay rates are never read. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create, change or permanently delete shifts and tasks, message a chat or one person, add, archive or delete users, and clock people in or out, which feeds their pay.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Connecteam tool, reads what it needs, and answers with the source cited.
These tools change something in Connecteam. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Connecteam for you. Each event can start a job, with the event as its input. Connecteam sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Connecteam 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.
Who is working on Saturday?
Which shifts next week are still open?
What tasks on the store opening board are overdue?
When is Dan Fletcher scheduled to work this week?
Assign Saturday's open warehouse shift to Dan Fletcher and let him know
On Friday the operations manager asks who is working at the Northwind site on Saturday. Memtro reads the scheduler's shifts for the day and lists each shift with its start and end and who is assigned, and flags the two shifts still open.
Priya Sharma asks Memtro to give Saturday's open shift at the Acme store to Dan Fletcher and tell him. Memtro changes the shift's assignee in Connecteam with notification switched on, so Dan sees the shift in his app, and nothing else on the schedule changes.
The teams that lean on Connecteam most, a question each of them asks, and what they connect beside it.
A record in Connecteam 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
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMConnecteam's API needs the Expert plan or higher, and an account owner or admin to create the key
In Connecteam open Settings → API Keys, choose Add API key, name it Memtro and copy the key, which is shown once
In Memtro open Connections → Connecteam, paste the API key, set Region to global if you sign in at app.connecteam.com or au if you sign in at app-au.connecteam.com, and connect
Ask who is on shift tomorrow
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Connecteam tools are the same everywhere.
Only when you ask, and only what it has been granted: create a quick task on a task board, as a draft or published to its assignees; change a quick task's title, status, assignees or dates; delete a quick task (permanent); create a shift in a schedule, notifying assignees only if asked; change a shift's time, assignees, title or published state, notifying only if asked; delete a shift (permanent), notifying only if asked; post a message in a team chat or channel as a custom publisher; send a private message to one person as a custom publisher; add an employee or manager, texting an activation link only if asked; change an employee's name, type, email or archived state; archive users, or delete them permanently; add a note to an employee's profile; clock a person in on a time clock; clock a person out on a time clock; create a job under schedules or time clocks. 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. Connecteam's API needs the Expert plan or higher, and an account owner or admin to create the key.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Connecteam for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
