Which Insightly opportunities moved this week, and what you hold on a contact.
Connect Insightly with your API key and pod, and Memtro reads contacts, searches contacts, opportunities and leads by a field value or by what changed since a date, and reads a project by its id. The key has your access, so Memtro sees what you see. 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 add notes, tags, contacts, organisations, opportunities, tasks and calendar events, mark an opportunity won or lost, move it to another stage, update tasks, and permanently delete an opportunity.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Insightly tool, reads what it needs, and answers with the source cited.
These tools change something in Insightly. 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 Insightly 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.
Insightly + MemtroWhich open opportunities changed since Monday?
What do we hold on the contact with email priya.sharma@brightwave.co.uk?
Which leads are rated 5?
What is the status of project 4471?
Mark the Northwind renewal opportunity as won
On Friday the sales lead asks what moved in Insightly this week. Memtro searches open opportunities changed since Monday and lists each with its fields, so the weekly review starts from what actually changed rather than from memory.
Dan Fletcher at Acme signs, and the account manager asks Memtro to mark the opportunity won and log the call. Memtro changes the opportunity's state to won, adds the note she approved, and creates a follow-up task owned by her.
The teams that lean on Insightly most, a question each of them asks, and what they connect beside it.
A record in Insightly 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.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapIn Insightly open User Settings → API and copy your API key, which has your access, so Memtro reads what you can see and can add what you could add
Note the Pod shown beside the key under API, the short code in your API URL such as na1 or eu1
In Memtro open Connections → Insightly, paste the API key and the Pod, and connect
Ask which opportunities changed this week, knowing Memtro searches by email before adding a contact, since Insightly does not refuse duplicates
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Insightly tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a contact, organisation, opportunity, lead or project; add a contact; add an organisation; create a task owned by the connection's user; create an opportunity; mark an opportunity won, lost, abandoned, suspended or open again; move an opportunity to another pipeline stage; add a calendar event; tag a contact, organisation, opportunity, lead or project; complete, reopen or edit a task's title, due date or details; delete an opportunity permanently. 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 and pod. In Insightly open User Settings → API and copy your API key, which has your access, so Memtro reads what you can see and can add what you could add.
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