Tracing a missing report
Maya Okafor, finance analyst at Acme Ltd, asked why the Board pack had stopped arriving. Memtro read the workbook's scheduled exports and found the schedule suspended, with its owner and when it last changed.
Which workbooks did finance update this month, and who receives them?
Sigma Computing answers questions about your BI estate. You see workbooks with their owners, versions and tags, each workbook's elements, the file tree of folders, data models and reports, teams, warehouse connections, scheduled exports and materialization jobs, and a member found by email. When asked and granted, Memtro can email a workbook as PDF, Excel or CSV to named people or teams, run a materialization, copy or version-tag a workbook, delete a scheduled export, add or deactivate a member and change a team's members. Worth knowing: the credentials act as their owner, so Memtro sees only what that person may.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sigma Computing tool, reads what it needs, and answers with the source cited.
These tools change something in Sigma Computing. 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 Sigma Computing 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.
Which workbooks did finance update this month?
Which charts and tables are in the Revenue overview workbook?
What scheduled exports does the Board pack workbook have?
Which warehouse connections have not been active lately?
Email the Weekly sales workbook as a PDF to the leadership team.
Maya Okafor, finance analyst at Acme Ltd, asked why the Board pack had stopped arriving. Memtro read the workbook's scheduled exports and found the schedule suspended, with its owner and when it last changed.
Dan Fletcher, head of finance at Northwind, asked Memtro to send the Weekly sales workbook as a PDF to the leadership team. Memtro exported it and Sigma emailed it to every member of that team.
The teams that lean on Sigma Computing most, a question each of them asks, and what they connect beside it.
A record in Sigma Computing 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 Sigma, go to Administration, then Developer access, choose Create new, tick REST API, name it Memtro and pick an owner with only the access Memtro needs.
In Memtro, open Connections → Sigma Computing and paste the API base URL shown at the top of Developer access, the Client ID and the Secret, which Sigma shows once.
An administrator grants the actions by name, such as Send workbook or Deactivate member, to the teams that may use them.
Ask which workbooks finance updated this month.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Sigma Computing tools are the same everywhere.
Only when you ask, and only what it has been granted: email a workbook as PDF, Excel or CSV to named people or teams; run a materialization for a workbook element (uses warehouse compute); copy a workbook into a folder; add a version tag to a workbook; delete a scheduled export (permanent); add a member, inviting them by email if you ask; deactivate a member; add or remove members of a team. 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 base URL, Client ID and Secret. In Sigma, go to Administration, then Developer access, choose Create new, tick REST API, name it Memtro and pick an owner with only the access Memtro needs.
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