Who is contracted through Deel, on which contract, and what hours they submitted.
Connect Deel with an organisation API token and Memtro reads contracts with worker, type, status, team and dates, people with job title, department, manager and country, timesheets, work items, time off and invoice adjustments. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can log hours, add work items or bonuses and expenses for review, request, approve, reject or cancel time off, and approve or decline work items and adjustments. Approving one decides what a contractor is paid, and deleting a work item is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Deel tool, reads what it needs, and answers with the source cited.
These tools change something in Deel. 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 Deel for you. Each event can start a job, with the event as its input. Deel signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Deel 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.
Deel + MemtroWho do we contract through Deel, and which legal entity is each contract under?
Which timesheets submitted last week are still pending?
Who reports to Dan Fletcher, and what are their job titles?
Which expenses are waiting for review this month?
Approve the two work items on the Brightwave design contract
Before month end the operations lead asks which timesheets are still pending. Memtro reads the month's submitted timesheets in Deel, grouped by contract, with hours, the date each covers and its status, so the lead knows whose approvals to chase.
Priya Nair asks Memtro to approve the travel expense a contractor added for the Northwind workshop. Memtro reads the pending adjustment, shows its amount and description, and once she confirms approves it in Deel, releasing the amount for the contractor's next payment.
The teams that lean on Deel most, a question each of them asks, and what they connect beside it.
A record in Deel 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
Factorial HR
Pinpoint
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
7shifts
Timetastic
Recruit CRMA Deel admin with Developer Center access opens Deel → More → Developer → Access Tokens, generates a new token and chooses Organization token
Tick organizations:read, contracts:read, people:read, timesheets:read, time-off:read and invoice-adjustments:read, which are enough to answer questions, and add a write scope such as timesheets:write or contracts:write only for the actions you want Memtro to take. Copy the token
In Memtro open Connections → Deel, paste the Organisation API token and connect
Ask who started this quarter, noting Deel allows 5 requests a second per organisation, shared by every token
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Deel tools are the same everywhere.
Only when you ask, and only what it has been granted: log hours on a Deel contractor's timesheet, for review; add a work item with an amount to a Deel pay-as-you-go contract, for review; approve or decline a work item on a Deel contract, which decides whether it is paid; permanently delete a work item from a Deel contract; request time off for a Deel worker under a policy; approve or reject Deel time-off requests; cancel a Deel time-off request, which cannot be reversed; add a bonus, commission, expense, deduction or other adjustment to a Deel contractor's invoice; approve or decline a Deel invoice adjustment, which decides whether it is paid. 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.
Organisation API token. A Deel admin with Developer Center access opens Deel → More → Developer → Access Tokens, generates a new token and chooses Organization token.
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 Deel 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
