Quick start
Connect a system, scan it, and read your first impact result. Ten minutes, no configuration file, no credit card.
1. Create a workspace
Sign up and name your workspace. The Free plan connects two systems and answers 25 questions a month, which is enough to see whether the graph tells you anything you did not already know.
2. Connect a system
Go to Integrations and connect the system you know best first, so you can sanity check the result against what you already believe. Eleven are available today:
| System | How it connects | What Meshie reads |
|---|---|---|
| SystemSalesforce | How it connectsOAuth | What Meshie readsObjects, fields, flows, layouts, reports, Apex, permission sets and profiles. |
| SystemHubSpot | How it connectsOAuth | What Meshie readsWorkflows and property references from your portal. |
| SystemSnowflake | How it connectsUser and password | What Meshie readsTable, view and column definitions, plus object dependencies. |
| SystemBigQuery | How it connectsService account JSON | What Meshie readsTable, view and column definitions, and view dependencies. |
| Systemdbt platform (formerly dbt Cloud) | How it connectsAPI token | What Meshie readsModel and source lineage from a job's latest run. |
| SystemFivetran | How it connectsAPI key and secret | What Meshie readsWhich upstream fields are actively synced. |
| SystemFivetran Activations (formerly Census) | How it connectsActivations personal access token and region | What Meshie readsReverse-ETL syncs: which fields feed which destinations. |
| SystemHightouch | How it connectsAPI key | What Meshie readsReverse-ETL syncs and models: which warehouse columns feed which destinations. |
| SystemMake | How it connectsAPI key | What Meshie readsScenario and module structure. |
| Systemn8n | How it connectsInstance URL and API key | What Meshie readsWorkflows, self-hosted or n8n Cloud. |
| SystemWorkato | How it connectsData center and API token | What Meshie readsRecipes: which app each step writes to, and the fields it maps. |
If you would rather not connect a live org yet, upload instead: Integrations accepts a .zip of sfdx-retrieved Salesforce metadata and builds the same graph from it.
3. Run a scan
Press Retrieve latest metadata on the connected row. Meshie retrieves that system’s metadata, parses it, and builds a snapshot: a set of nodes and the edges between them. The Overview page will show you the counts when it finishes.
Connect a second system and scan that too. This is the point of the product: a single system’s graph is something that system could have told you itself.
4. Ask what breaks
Open Impact, search for a field you were thinking of changing, and read the verdict. You will get one of three answers, and the difference between the last two is the reason Meshie exists:
- In use. Here is everything that references it, grouped by system, each with the file it came from.
- Nothing references this. No reference in the latest scan.
- Can’t confirm this is unused. Something reaches it through a reference Meshie cannot resolve, so it may still be in use. See Unknown edges.
5. Take it out of the browser
The same queries run locally, with no account at all, against a metadata export:
uv tool install git+https://github.com/cr-digital-services/meshie.git
meshie scan --source ./force-app
meshie impact salesforce:CustomField:Account.Status__cOr against your workspace, which is how you would wire this into CI. That path needs a CLI token, which is a Pro feature; the local commands above work on any plan.
- Settings, CLI tokens, create one. The secret is shown once and stored only as a hash, so copy it then.
meshie remote login --token <secret> --workspace <slug> --api-url https://meshie.aimeshie remote impact <node-id> --json
From there, the CI gate guide turns it into a check that fails a pull request touching a field something else depends on.