Morning sync check
Sarah Chen, revenue operations lead at Northwind, asked whether the Salesforce sync failed last night. Memtro read the sync's runs and showed one failed run with 340 rows failed and the start of the error Salesforce returned.
Did the Salesforce sync in Hightouch fail last night, and why?
Hightouch moves warehouse data into your business tools. Memtro reads your syncs with their status, schedule and last run, and each sync's runs with rows planned, succeeded and failed and any error, plus the sources, destinations and models behind them. When asked, and once an administrator has granted the action by name, it can run a sync or a sequence now, which writes to the destination system for good using warehouse and destination quota, run an identity graph, pause or resume syncs, approve or reject sync drafts, and permanently delete a sync. The SQL behind a model is never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Hightouch tool, reads what it needs, and answers with the source cited.
These tools change something in Hightouch. 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 Hightouch, choosing the same kinds; the tab shows Hightouch's own steps. Each event can start a job, with the event as its input. Hightouch sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Hightouch 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.
Did the Salesforce sync fail last night?
Which Hightouch syncs are failing?
How many rows failed on the HubSpot contacts sync this week?
Which syncs feed the Google Ads destination?
Rerun the Salesforce accounts sync now
Sarah Chen, revenue operations lead at Northwind, asked whether the Salesforce sync failed last night. Memtro read the sync's runs and showed one failed run with 340 rows failed and the start of the error Salesforce returned.
Dan Fletcher, data engineer at Acme Ltd, fixed a field mapping in Salesforce and asked Memtro to rerun the accounts sync. Memtro started the run in Hightouch, which wrote the changed rows to Salesforce, then read the run and reported every row succeeded.
The teams that lean on Hightouch most, a question each of them asks, and what they connect beside it.
A record in Hightouch 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 app.hightouch.com, open Settings → API keys → Add API key. Only a workspace admin can create one, and a key belongs to one workspace.
Scope the key to a user group with the Workspace viewer role for reads, or one that may run and edit syncs if Memtro should act, and copy it. It is shown once.
In Memtro, open Connections → Hightouch and paste it as API key.
Ask: did the Salesforce sync fail last night?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Hightouch tools are the same everywhere.
Only when you ask, and only what it has been granted: run a sync now, sending its rows to the destination (optionally a full resync or clear and refill); run a sync sequence now; run an identity resolution graph now; pause a sync's schedule, or resume it; delete a sync permanently; approve a sync draft, applying its change, or reject it. 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. In app.hightouch.com, open Settings → API keys → Add API key. Only a workspace admin can create one, and a key belongs to one workspace.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Hightouch, choosing the same kinds; the tab shows Hightouch'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