The systems Runmate reads from.
Connected
Each connected app shows how many records Runmate has from it and when it last synced. Sample data means a sandbox using made-up records; Connected means your live system; Needs attention means the last sync failed, with the reason.
Open What Runmate sees and won't do on any app to see exactly what it reads and the things it never does, like changing records or sending your data to an AI provider that trains on it.
Connecting an app (Client admin)
Apps marked Ready to connect can be connected now, with your own account:
- Open the app and follow the steps on screen to create a read-only key in that app (or sign in, for apps that support it).
- Paste the details. Runmate checks them with the app before saving, and stores them encrypted.
- Choose what Runmate may read: each record type (orders, customers, stock…) can be on or off. Runmate syncs only what's on.
- Select Check and connect. The first sync starts within a minute, then Runmate keeps up every 15 minutes.
What Runmate may do
Some apps also list things Runmate can do, like creating a draft product in Shopify. Every one is off until a Client admin turns it on, and shows its risk and the permission the app needs. When Runmate does something:
- it's held in Approvals by default, with a preview of exactly what will happen;
- lower-risk actions can be set to run without approval when no guardrail holds it; high-risk ones (like publishing a product customers can buy) always need approval;
- messages to anyone outside your company always need approval (rule BASE-07);
- everything is in the audit log, and the same request never runs twice.
What Runmate may do
Some apps also list things Runmate can do, like creating a draft product in Shopify. Every one is off until a Client admin turns it on, and shows its risk and the permission the app needs. When Runmate does something:
- it's held in Approvals by default, with a preview of exactly what will happen;
- lower-risk actions can be set to run without approval when no guardrail holds it; high-risk ones (like publishing a product customers can buy) always need approval;
- messages to anyone outside your company always need approval (rule BASE-07);
- everything is in the audit log, and the same request never runs twice.
On the app's page you can change permissions, Sync now, or Disconnect. Disconnecting deletes the stored credentials, and the synced data too if you choose. Runmate only reads; making changes in an app will need an action you turn on, with approvals.
If a sync fails, the app shows Needs attention with the reason, such as a revoked key. Reconnect to fix it.
Spreadsheet upload (Client admin)
For any system Runmate doesn't connect to yet, upload an Excel file (.xlsx) or a CSV, up to 10 MB and 50,000 rows. For an Excel file with several sheets, choose which sheet to upload; each sheet can be its own dataset. Formulas come in as the values Excel last calculated. Hidden sheets are skipped. Older .xls files need saving as .xlsx first.
- Choose the file. Runmate reads the columns, guesses each one's type, and suggests how sensitive it is from its name (for example, "email" is contact details, "cost" is cost and margin).
- Name the data, choose which columns to include, and correct the sensitivity where needed. Pick a date column if the rows have one.
- Select Upload. Ask, runs and dashboards can use it straight away, with the same masking and hiding as connected apps.
Uploading again under the same name replaces the data. Files containing card or social security numbers are refused, and nothing is stored. You can delete uploaded data at any time.
Available
Other apps are grouped by type. With the pilot apps open first; Coming later apps are built as companies ask for them. Use the search box to find one, and tell your Runmate contact which you use.
Guardrails apply to everything
Whatever comes in from an app goes through your company's guardrails, so masked and hidden fields stay that way in every answer and run.