Ask which Fivetran pipelines are failing, and when each source last loaded successfully.
Connect Fivetran with an API key and secret and Memtro reads your connections (pipelines) with source, destination group, schedule, state, last success and last failure, setup tasks and warnings, along with destinations, groups and users. A connection's configuration, which holds the source's credentials, is never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can start a sync or a full historical re-sync, both consuming credits, pause or resume a connection, change how often it syncs, and run its setup tests.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fivetran tool, reads what it needs, and answers with the source cited.
These tools change something in Fivetran. 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 Fivetran 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 Fivetran pipelines are broken right now?
When did Salesforce last load into the warehouse?
Which connections are paused, and who connected them?
Run the setup tests on the Stripe connection
Sync the HubSpot connection now
The finance lead at Brightwave Ltd asks why yesterday's revenue figures are missing. Memtro checks Fivetran and finds the Stripe connection failing since 02:10 with a warning to reauthorise, while the other nine pipelines into the warehouse succeeded overnight.
After the Stripe connection is reauthorised, Laura Bennett asks Memtro to load it now rather than wait for the schedule. Memtro starts a sync of that one connection, which loads the new and changed rows into the warehouse and uses credits for them, and reports when the last success time moves.
The teams that lean on Fivetran most, a question each of them asks, and what they connect beside it.
A record in Fivetran 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.
Grist
NocoDB
Typesense
Weaviate
Tinybird
Hightouch
Census
kintone
Monte Carlo
OpenMetadata
Secoda
Softr
Teable
VectaraIn the Fivetran dashboard open your user menu (bottom left) → API Key and generate a key. If the menu differs, look for API Key in your user or account settings
The key acts as your user and can do what your role can do. Account administrators can instead make a system key under Account settings → General → System Keys
In Memtro open Connections → Fivetran, paste the API key and the API secret shown beside it (the secret is shown once), and connect
Ask which pipelines failed their last run
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fivetran tools are the same everywhere.
Only when you ask, and only what it has been granted: start a sync of a connection now (consumes credits); run a full historical re-sync of a connection or named tables (consumes credits); pause a connection; resume a paused connection; change how often a connection syncs; run a connection's setup tests. 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 key and API secret. In the Fivetran dashboard open your user menu (bottom left) → API Key and generate a key. If the menu differs, look for API Key in your user or account settings.
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
