Ask what open Pylon issues an account has, and what the customer said in each.
Connect Pylon with an API token and Memtro reads issues by state, assignee, account, tag or date with their messages and internal notes, accounts with owner and latest activity, contacts, tasks, team members and knowledge-base articles. The hourly sync writes Pylon issues into memory. When asked, and once an administrator has granted the action by name, it can reply to a customer on an issue, which cannot be unsent, add notes, change, snooze, merge or permanently delete issues, manage accounts, contacts and tasks, draft or publish articles, and invite a person by email to the Pylon organisation.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Pylon tool, reads what it needs, and answers with the source cited.
These tools change something in Pylon. 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, then add the address it shows as a webhook in Pylon, choosing the same kinds; the tab shows Pylon's own steps. Each event can start a job, with the event as its input. Pylon signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Pylon 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.
What open issues does Acme have, and who is on them?
Which issues have been waiting on us since Friday?
What did Northwind say in their latest ticket?
Reply on issue 482 that the fix ships Thursday
Merge Globex's two duplicate login issues into the older one
The account lead asks what is open for Brightwave Ltd before a quarterly review. Memtro searches issues by account and reads each one: three open, one waiting on engineering for a week, with the customer's last message and the internal note on each.
Dan Fletcher asks Memtro to tell BigCo on issue 482 that the fix ships Thursday. Memtro shows him the reply, and once he approves the words it sends it on the issue's channel, where the requester receives it, then moves the issue to waiting on customer.
The teams that lean on Pylon most, a question each of them asks, and what they connect beside it.
A record in Pylon 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.
Freshdesk
Gorgias
Crisp
Groove
Plain
Freshchat
Freshservice
Kustomer
Dixa
HelpCrunch
Custify
Atera
Trengo
ConnectWise PSA
Enchant
Frill
Gladly
HaloPSA
HappyFox
Jitbit Helpdesk
Nicereply
Re:amaze
SolarWinds Service Desk
Stonly
Syncro
Tidio
Teamwork DeskIn Pylon open Settings → Integrations & dev → API tokens → Create API Token. Only Pylon Admins can create one, and it is shown once
The token has no scopes: its role is the only control, so give it a dedicated user or the narrowest role that covers what Memtro may do. Inviting teammates needs an admin role
In Memtro open Connections → Pylon, paste the API token and connect. The region comes from the token. If you allowlist IPs for API tokens, add Memtro's address
Ask what open issues Acme has
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Pylon tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to an issue; create an internal issue on an account (no customer is contacted); create a task; add an internal comment to a task; reply to a customer on an issue (they receive it); save a private draft reply on an issue (not sent); change an issue's state, assignee, team, title, type or tags; snooze an issue until a time; add or remove followers on an issue; merge duplicate issues into one (permanent, an optional closing message reaches each customer); delete an issue (permanent); create a customer account; update an account's name, owner, domains, type, tags or disabled flag; create a contact on an account (no portal access unless asked); update a contact's name, email or account; update a task's title, details, status, assignee, due date or project; create a knowledge-base article as an unpublished draft; edit a knowledge-base article, publishing only when asked; invite a person to the Pylon organisation (emails an invitation). 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 Pylon records into memory as entities.
API token. In Pylon open Settings → Integrations & dev → API tokens → Create API Token. Only Pylon Admins can create one, and it is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Pylon, choosing the same kinds; the tab shows Pylon's own steps. 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