Failing syncs on Monday
Priya Sharma, marketing operations manager at BigCo, asked which Census syncs were failing. Memtro listed two marked failing, each with its operation, destination object and schedule frequency.
Which Census syncs are failing, and how many records did they drop?
Census, now Fivetran Activations, sends warehouse data to your business tools. Memtro reads your syncs with status, operation, schedule and whether paused, and each sync's runs with records processed, failed and invalid, and any error. It reads the sources, activations and datasets behind them too. When asked, and once an administrator has granted the action by name, it can run a sync now, which writes changed records to the destination system where they stay, pause or resume a sync, cancel a running run, and permanently delete a sync. Dataset SQL is never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Census tool, reads what it needs, and answers with the source cited.
These tools change something in Census. 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 Census 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 Census syncs are failing?
Why did the HubSpot upsert sync fail this morning?
How many records were invalid on the last Salesforce run?
Which Census syncs are paused?
Pause the HubSpot upsert sync until Monday
Priya Sharma, marketing operations manager at BigCo, asked which Census syncs were failing. Memtro listed two marked failing, each with its operation, destination object and schedule frequency.
Tom Reilly, analytics engineer at Northwind, asked Memtro to pause the Salesforce sync while the sales team cleaned up duplicate accounts. Memtro paused it in Census, so it stopped running on its schedule. When the clean-up was done he asked again, and Memtro resumed it and started one run.
The teams that lean on Census most, a question each of them asks, and what they connect beside it.
A record in Census 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 Census, open User settings → Personal Access Tokens → New Token. The token has its creator's permissions, so create it as a user with read-only access unless Memtro should run, pause or delete syncs.
Name it Memtro and copy it. A Fivetran PAT or an old V1 workspace API key does not work here.
In Memtro, open Connections → Census, paste it as Personal access token, and set Region to eu if you sign in at app-eu.getcensus.com.
Ask: which Census syncs are failing?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Census tools are the same everywhere.
Only when you ask, and only what it has been granted: run a sync now, sending changed records to its destination (optionally a full sync); pause a sync, or resume a paused one; cancel a running sync run; delete a sync 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.
Personal access token and optional region. In Census, open User settings → Personal Access Tokens → New Token. The token has its creator's permissions, so create it as a user with read-only access unless Memtro should run, pause or delete syncs.
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