Ask what you know about a contact in Nimble and what is planned with them.
Connect Nimble with an API token and Memtro reads people and companies with name, email, title, company, tags and owner, a contact's non-private fields and notes, deal pipelines, and the activity timeline of tasks, calls, meetings and events. Phones and addresses are not returned. 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, create tasks, create and update contacts, tags and deals, and permanently delete a contact or deal, which Nimble cannot restore. Deals record possible sales and move no money.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Nimble tool, reads what it needs, and answers with the source cited.
These tools change something in Nimble. 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 Nimble 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.
Nimble + MemtroWhat do we know about Priya Nair at Brightwave Ltd?
Which calls and meetings are coming up with Acme?
What were the last notes on Dan Fletcher?
Create a task to send BigCo the onboarding plan by Friday
Move the Globex renewal deal to the proposal stage at 12,000 pounds
Before meeting Northwind, the founder asks what the team knows about Priya Nair. Memtro reads her Nimble contact with title, company and custom fields, the last three notes and the call booked for Thursday, and says where things stand.
After a call, Dan Fletcher asks Memtro to log it against Brightwave Ltd and move their deal on. Memtro adds a note to the contact, moves the deal to the proposal stage with the agreed amount, and creates a follow-up task for two weeks out, which Dan sees in Nimble.
The teams that lean on Nimble most, a question each of them asks, and what they connect beside it.
A record in Nimble 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
Insightly
Nutshell
Vitally
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapOnly a Nimble account administrator can generate the token: open Settings → API Token → Generate New Token, name it and choose its scopes
Choose contacts, and deals if Memtro should work with deals, then on Settings → Users make sure API access is enabled for your user
Copy the token, then in Memtro open Connections → Nimble, paste the API token and connect
Ask what is planned with Northwind this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Nimble tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a contact; create a task, optionally linked to contacts; add a note to a deal; create a contact (person or company); update a contact's fields; set a contact's tags to a given list; create a deal; update a deal; delete a contact permanently; delete a deal 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 token. Only a Nimble account administrator can generate the token: open Settings → API Token → Generate New Token, name it and choose its scopes.
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