Friday pipeline stand-up
The SDR lead asks how the Q4 Outbound cadence is doing. Memtro returns the people on it, how many were acted on, the meetings booked and opportunities created, and the overdue call tasks still sitting with each rep.
Who is on which cadence, who was reached and what is overdue, from Salesloft.
Connect Salesloft with an API key and Memtro reads people with their account, owner and cadence, accounts, cadences, calls and emails by person or date, open and overdue tasks, and users. Every hour it writes each person added to Salesloft into memory. When asked, and once an administrator has granted each action by name, it adds notes, creates people and tasks, updates or completes tasks, and adds people to cadences or removes them. Adding someone to a cadence starts its emails and calls to that person outside the company, and notes and new people may reach your connected CRM.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Salesloft tool, reads what it needs, and answers with the source cited.
These tools change something in Salesloft. 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 Salesloft for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Salesloft signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Salesloft 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 on the Q4 Outbound cadence and how many meetings has it booked?
Which of Tom's calls connected last week and what was the disposition?
Which tasks are overdue across the team today?
Add a note to Dana Reyes at Brightwater: she asked us to call back after 15 November
Put the three new Globex contacts on the Q4 Outbound cadence
The SDR lead asks how the Q4 Outbound cadence is doing. Memtro returns the people on it, how many were acted on, the meetings booked and opportunities created, and the overdue call tasks still sitting with each rep.
Dana Reyes rings back. Chris Hall asks what has happened with her and Memtro returns every cadence she has been on, the last emails and calls with their outcomes and the open task. He then asks it to note the call and move the task to next Tuesday, and Memtro does both, the note syncing on to the CRM.
The teams that lean on Salesloft most, a question each of them asks, and what they connect beside it.
A record in Salesloft 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.
In Salesloft open the account menu → Your Applications → API Keys → Create New, name the key and tick people, accounts, cadences, activities, tasks and users: read
For the actions also tick notes: write, people: write, cadence memberships: write and tasks: write, only for the ones an administrator will grant
Save and copy the key, then in Memtro open Connections → Salesloft, paste the API key and connect. The key acts as the user who made it, and an admin's key sees the whole team
Ask who was reached last week or which tasks are overdue
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Salesloft tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a person or account; create a person; add a person to a cadence, which starts its emails and calls to them; remove a person from a cadence; create a task for a person; reschedule, reassign or complete a task. 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. An hourly sync anchors recently changed Salesloft records into memory as entities.
API key. In Salesloft open the account menu → Your Applications → API Keys → Create New, name the key and tick people, accounts, cadences, activities, tasks and users: read.
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 Salesloft 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