Publish Integration Compatibility Tables From Product Team Excel Files

Keep integration pages current from the same source sheet.

Product and partnerships teams usually track connector status in spreadsheets with version support and known limitations.

Before: compatibility pages are hand-edited and outdated.

After: the same matrix is published as a filterable table by platform and support level.

Main friction point: Customers choose the wrong integration path when status pages lag behind product updates.

Create Your First Table

A concrete example

A customer planning a CRM rollout checks whether their current version is supported and sees documented limitations in the same view.

Example spreadsheet for this post: Download Example Sheet

Categories

Integration Platform version Support level
Salesforce v59 Full
HubSpot v3 Full
NetSuite 2025.2 Partial
Dynamics 365 9.2 Full
SAP B1 10.0 Limited
Last tested Known limitation Owner team Documentation link

Powered by

TableMaker

2026-03-18 Bulk upsert capped at 10k Integrations /docs/sf
2026-03-17 Custom objects beta only Integrations /docs/hubspot
2026-03-12 No item matrix sync ERP /docs/ns
2026-03-15 OAuth app registration needed Integrations /docs/d365
2026-03-09 Read-only inventory endpoint ERP /docs/sapb1

Why a web table works better for this use case

A web table is easier to use when people need to:

Customers can verify compatibility before onboarding.

CS teams can reference one up-to-date integration table.

Product ops can update status without page rewrites.

What this usually looks like in the spreadsheet

A typical spreadsheet for this workflow might include:

Integration

Platform version

Support level

Last tested

Known limitation

Owner team

Documentation link

A practical way to publish it

1

Upload the compatibility matrix

  • Include support level and last-tested date.
  • Keep one row per integration-version pair.

2

Configure practical filters

  • Enable filters for platform and support level.
  • Sort by last tested date.

3

Embed on integration docs pages

  • Place near setup guides.
  • Reimport as compatibility changes.

Final thoughts

If you already have the spreadsheet, start with that file and publish one table for your next stakeholder review.

Create Your First Table