Which Workiz jobs are open this week, and who is assigned to them?
Workiz connects Memtro to your field-service management. It reads jobs and leads with status, type, source, schedule, service area, tags, assigned technicians and notes, and your team with roles, skills and service areas. When asked and granted, it can create or update a job or lead, convert a lead to a job, mark a lead lost or reactivate it, assign or unassign a technician, and record a payment against a job. Client contact details and prices are never returned. Writes need the API secret issued with the token, so a connection without it can only read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Workiz tool, reads what it needs, and answers with the source cited.
These tools change something in Workiz. 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 Workiz 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.
Workiz + MemtroWhich open jobs are scheduled this week, and who has them?
Which leads came in from Google in the last two weeks?
What notes are on job XYZ56X?
Which technicians cover the North service area?
Mark lead 4471 as lost.
Tom Reilly, operations manager at Northwind, asked which open jobs were scheduled for tomorrow and who had them. Memtro listed them with type, service area, time and assigned technicians, and flagged the ones with nobody assigned. He gave those to the technicians covering that area.
Priya Sharma, office manager at Acme Ltd, asked Memtro to record a cash payment a customer had handed a technician, with the amount and date she gave. With the action granted, Memtro recorded it against the job, which changed the job's amount due. Nobody was charged.
The teams that lean on Workiz most, a question each of them asks, and what they connect beside it.
A record in Workiz 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.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Guesty
Buildium
Skilljar
Runn
ClockodoFind the account API token Workiz issues for API access, the part of the API address after /api/v1/. If it is not in your Workiz settings, Workiz support can issue it. The auth secret, starting sec_, is issued with it.
In Memtro, open Connections → Workiz and paste the API token. Add the API secret too if Memtro should make changes, or leave it empty for a read-only connection.
An administrator grants the job, lead, assignment and payment actions by name to the teams that may use them.
Ask which open jobs are scheduled this week and who has them.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Workiz tools are the same everywhere.
Only when you ask, and only what it has been granted: create a job; update a job's status, schedule, type, notes or tags; create a lead; update a lead's status, schedule, type, notes or tags; convert a lead to a job; mark a lead as lost; reactivate a lost lead; assign a team member to a job; unassign a team member from a job; assign a team member to a lead; unassign a team member from a lead; record a payment against a job. 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 token. Find the account API token Workiz issues for API access, the part of the API address after /api/v1/. If it is not in your Workiz settings, Workiz support can issue it. The auth secret, starting sec_, is issued with it.
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