Meshie

Integrations

Your GTM stack in. One map out.

Meshie connects to the tools your GTM data actually moves through, reads how each one is configured, and links them together down to the field and the picklist value. That map is what Meshie checks every change against. It reads configuration, never records.

Try it on your stack freeFree includes any two systems.

  • Each system describes itself.

    Meshie reads each tool's own configuration: fields, workflows, syncs, models.

  • Meshie connects the descriptions.

    A Fivetran Activations sync names the Salesforce field it writes. A HubSpot workflow branch matches a picklist value. A dbt™ model reads a warehouse table that Fivetran loaded from Salesforce. Those become links on the map.

  • Every link says how sure it is.

    Read directly from config, matched by name, or observed from activity. Anything ambiguous is flagged, never guessed.

See one value traced across systems →

CRM

  • SalesforceThe center of most maps.
    Reads
    objects, custom fields, picklist values (including standard and global value sets), record types, validation rules, flows, workflow rules, Apex classes and triggers, layouts, Lightning pages, reports, email templates, permission sets and profiles.
    Links to
    HubSpot properties and picklist values, Fivetran Activations and Hightouch syncs, Fivetran columns and everything downstream of them in the warehouse.
    Also sees
    every connected app and integration user in the org, which fields each integration user can edit, and which of them have actually written to history-tracked fields in the last 90 days. Plus who changed what in Setup, from the Setup Audit Trail.
    Never reads
    Leads, Contacts, Accounts, Opportunities or any other business records. The only queries beyond metadata are setup data (users, permission assignments, audit trail) and aggregate counts of field-history writes, never the values.
    Connect with
    OAuth, production or sandbox. The person connecting needs to be a Salesforce System Administrator or hold the "Approve Uninstalled Connected Apps" permission, or an admin approves Meshie once in Setup. Or upload a metadata retrieve if you'd rather not connect.

    Without "View Setup and Configuration", Meshie still maps your metadata and tells you the Setup Audit Trail part couldn't be checked.

    Rename a Salesforce Picklist Value Safely
  • HubSpotWhere Salesforce values quietly get matched.
    Reads
    contact, company and deal properties, every option of every dropdown property, and workflows, including the values their filters and branches match on.
    Links to
    Salesforce picklist values (by matching option names on mapped objects), Fivetran Activations and Hightouch syncs, Fivetran columns.
    Never reads
    contacts, companies, deals or any CRM records. Meshie requests schema and automation scopes only, no record-read scopes.
    Connect with
    OAuth.

    Limit: custom objects are not read yet.

    HubSpot Salesforce Picklist Sync Errors, Explained

Warehouse and transformation

  • SnowflakeBeta
    Reads
    tables, views and columns in the database you connect, plus view and table dependencies.
    Links to
    the Salesforce and HubSpot fields each column came from (through Fivetran), and the dbt models built on top.
    Also sees
    which client applications (BI tools, sync tools) connect to the warehouse, from session history.
    Never reads
    table rows.
    Connect with
    a read-only service account. Dependency and client-app detection need access to Snowflake's account usage views; without it, Meshie tells you what it couldn't check.
  • Google Cloud BigQueryBeta
    Reads
    tables, views, columns and view dependencies for one dataset.
    Links to
    the hub fields each column came from (through Fivetran), and dbt models.
    Never reads
    table rows. Access is read-only.
    Connect with
    a service account key.
  • dbt platform(formerly dbt Cloud)Beta
    Reads
    models, sources and their dependencies, and documented columns, from a job's latest successful run.
    Links to
    the warehouse tables and columns each model reads.
    Never reads
    warehouse data.
    Connect with
    a service token and job ID.
    Salesforce field changes that break dbt and reverse ETL
  • FivetranBeta
    Reads
    your connectors and their schema settings: which tables and columns are synced, and where they land.
    Links to
    the Salesforce or HubSpot field each column comes from, and the warehouse column it lands in. This is the bridge that connects your CRM to your warehouse on the map.
    Never reads
    synced data. Only names.
    Connect with
    API key and secret.
    Salesforce field changes that break dbt and reverse ETL

Reverse ETL

  • Fivetran Activations(formerly Census)Beta
    Reads
    syncs, sources, destinations and each sync's field mappings.
    Links to
    the exact Salesforce or HubSpot field each sync writes, and the exact picklist value when a sync writes a fixed value.
    Never reads
    synced rows.
    Connect with
    API token.
    Salesforce field changes that break dbt and reverse ETL
  • HightouchBeta
    Reads
    syncs, models, sources and destinations, and the fields each sync maps.
    Links to
    Salesforce and HubSpot fields and picklist values the syncs write.
    Never reads
    synced rows.
    Connect with
    API key.
    Salesforce field changes that break dbt and reverse ETL

Automation

  • Make
    Reads
    scenario blueprints: every module and what it maps from the modules before it.
    Links to
    the apps each scenario touches, and the field references between its steps.
    Never reads
    execution history or the data that ran through it.
    Connect with
    an API token scoped to read scenarios.
  • n8n
    Reads
    workflows: every node and the expressions that pass fields between them. Self-hosted or n8n Cloud.
    Links to
    the apps each workflow touches, and field references between nodes.
    Never reads
    executions or stored credentials.
    Connect with
    instance URL and API key.
  • WorkatoBeta
    Reads
    recipes: every step, the datapills passed between them, and which connections each recipe uses.
    Links to
    the apps and specific accounts each recipe touches (it can tell two Salesforce connections apart), and field references between steps.
    Never reads
    job history or the data that ran through it.
    Connect with
    an API client token.

Automation tools show what each workflow touches and how data moves between its steps. Field-level links from these tools into Salesforce or HubSpot fields are not drawn yet.

Free connects any two systems. Pro connects every system we support. Enterprise has no limit.

Using an agent? Any agent that speaks MCP can read the same map.

Don't see your tool?

Meshie often sees it anyway.

Most GTM tools that write to your CRM leave a trace in Salesforce: a connected app, an integration user, permissions on the fields it edits, and a history of what it wrote. Meshie reads those traces from the Salesforce side, so tools like Gong, Outreach, ZoomInfo or Clay show up on the map as the systems writing to your fields, even without a direct connection.

What that can't show is what the tool read to decide what to write. Where a direct connection would add that, we're working on it.

Not yet connectable, and why

  • Clay: no API exposes table configuration yet.
  • Zapier: no API exposes a Zap's step configuration.
  • Segment: the API we'd need is still in alpha.
  • Marketo: on the list; we won't ship it until we can test against a live instance.
Tell us what you run →

Configuration in. Records never.

For every system, Meshie reads how it's set up, not what's in it. No Lead, Contact, Deal or table row is ever ingested or stored. Where a vendor offers read-only or schema-only access, Meshie asks for that and nothing more.

Read our security page →

All product names, logos and trademarks are the property of their respective owners. Their use here indicates compatibility, not endorsement or partnership.