Skip to main content
Orvianlaunch home

This week is in orbit

Listing Integrations Clearly: What Connects and How

Integrations · 10 min read ·

How to describe what your product connects to, so buyers and assistants can tell what works, how deeply and with what limits, without vague logo walls.

Illustration: A midnight-navy table-like diagram: rows of tool nodes with small arrows showing direction, a column for status and a column for limits

A grid of logos is the most common way to say "we integrate with everything". It is also among the least informative. A reader who sees forty logos learns that the product has some relationship with forty brands, and nothing about what the relationship is: whether data flows in or out, whether it is one click or a day of setup, whether it covers the whole of the other tool or one small corner.

Clear integration listings are one of the most useful pages a product can publish. They help buyers decide quickly, they reduce support questions and they give search engines and assistants accurate facts to quote. This guide explains how to list integrations so that they inform instead of impress.

What an integration is, precisely

Interoperability is the ability of systems to exchange and use information. An integration is a specific implementation of that ability between two products: a defined way in which your product and another one share data or trigger actions in each other.

Integrations come in many forms. Some are built in, in which the two products connect directly. Some work through a third-party connector service that links many tools. Some use a documented open interface, so that anyone with the skills can build the connection. Some are manual, such as importing and exporting files. Each is legitimate, and each is a different promise.

The problem with logo walls

A logo wall fails for several reasons.

  • No depth. A logo can mean a full, two-way sync or a single export button.
  • No direction. Does data flow into your product, out of it or both?
  • No limits. Which features, record types or plans are covered?
  • No setup information. Is it one click or a custom project?
  • Implied endorsement. Using another company's logo may suggest a partnership or approval that does not exist, and may breach their brand rules.
  • Poor accessibility. Logos in images may have no text for screen readers, and do not help search.
  • Staleness. Logos linger long after a connection has stopped working.

If you must show logos for visual recognition, pair them with text and a link to a full list.

What each entry should say

Think of each integration as a short factsheet. The following fields cover most needs.

Name. The other tool's name, spelled correctly, with its category.

What it does. One sentence describing the job in plain words: "Sends each new order to a spreadsheet row", "Creates a task for every approved invoice".

Direction. One-way into your product, one-way out or two-way. State which.

Type. How it is delivered: built in, via a connector service, via the open interface or manual file exchange.

Coverage and limits. What is included and what is not: record types, fields, volume limits, plan requirements, supported versions or regions.

Setup. How long it takes, who can do it and whether it needs special permissions. A link to a guide.

Status. Available, beta, deprecated or planned. With a date of the last check.

Support. Where to get help with this integration.

Cost. Whether it is included in all plans or only some, with the pricing shown from its source of truth elsewhere on the site, so that figures do not go stale.

Not every field needs a paragraph. A line each, in a consistent format, is plenty.

Be honest about type and depth

The difference between a built-in integration and a workaround matters to buyers, and mislabelling it is a quick route to disappointment.

  • Built in: a direct connection, maintained by you. Say so.
  • Via a connector service: works through a third-party tool that links many products. Name it and note that it may involve another account and cost.
  • Via the open interface: the connection is possible, but someone has to build it. Link to the documentation. An interface description, such as one following a common specification, helps developers see what is possible.
  • Manual or file-based: import and export of files. Not a live connection. Label it so.
  • Community-built: made by others, not supported by you. State who maintains it.

Do not blur these. A buyer who expects a live two-way sync and finds a CSV export will feel misled, however true the logo was.

Organise for the reader

A long list needs structure.

  • Group by category: accounting, messaging, storage, calendars, analytics. Readers look for the tool they use.
  • Offer search or filtering, if the list is long.
  • Lead with the most used, or the deepest.
  • Use consistent entry format, so entries can be compared.
  • Give each important integration its own page, with detail, setup steps and examples, and link from the list.
  • Provide a plain-text version, not only visual elements, so that it is accessible and indexable.

Think of the list as a directory. A good directory answers "does it connect to X?" in seconds.

Documentation and examples

Integrations are easier to trust when they come with documentation. Software documentation, the written material that explains how software works and how to use it, is part of the product.

For each important integration, offer:

  • A short setup guide, with screenshots, that a user can follow in minutes.
  • A description of what data moves and how often.
  • Known limits and troubleshooting tips.
  • A worked example, showing a real result.
  • A changelog, so users see when it changed.

For the open interface, provide reference documentation, examples in common languages and a test environment where possible. Details of what this product exposes to developers are on the developers page.

Handling planned and community integrations

Readers like to know what is coming, but planned items can mislead if not handled carefully.

  • Keep planned items in a separate section, labelled "Planned, not yet available".
  • Avoid dates unless you are confident.
  • Do not display planned logos next to live ones.
  • Invite requests, with a simple form or contact.
  • Remove items that you no longer intend to build, or say they are not planned.

Community-built integrations are useful but carry a different level of assurance. Label them, link to their source and say who supports them.

Keeping it true

An integrations page decays quickly. Platforms change, and your own code changes.

  • Assign an owner for the list.
  • Review it regularly, at least quarterly, and after any change to a connection.
  • Test integrations periodically, as part of your release process.
  • Mark the last-checked date on each entry.
  • Retire dead integrations, with a note and, where affected users exist, a notice.
  • Watch for changes in other platforms' interfaces, terms and branding rules.
  • Correct errors quickly, and thank users who report them.

A page that says "last checked 14 March" is more credible than one with no date. A page that lists a connection that stopped working a year ago is worse than none.

Machine readability

Search engines and assistants answer questions such as "does this tool work with X?" by reading pages. Make it easy for them.

  • Write the facts in text, in a consistent form: "Works with [tool]: sends [data] to [tool] automatically."
  • Use clear headings and lists.
  • Include the tool names, spelled as the other company writes them.
  • Avoid hiding the content in images, scripts or collapsed sections that cannot be read.
  • Provide structured data where appropriate, following search engine guidance.
  • Keep the claims accurate. An assistant that repeats an overclaim will repeat it widely.

Accuracy matters even more than usual when your words may be quoted without the context of your page.

Using another company's name and logo involves some care.

  • Check their brand guidelines. Many publish rules for referring to integrations.
  • Do not imply partnership, unless one exists. "Works with" or "integrates with" is usually acceptable; "official partner" is not unless true.
  • Use names correctly, including capitalisation.
  • Respect trademarks.
  • Be accurate about what is supported, so that you do not make claims about another company's product that they would dispute.

A worked example

A small company has an integrations page with thirty-two logos in a grid. Support receives frequent questions: does it sync both ways with the accounting tool, does the calendar one work with shared calendars, is the chat one included on the cheapest plan? The team decides to rewrite the page.

For each of the twelve integrations that actually work, they write an entry: name, one-line job, direction, type, limits, setup time and status. The accounting tool is "built in, two-way sync of invoices and payments, set up in about five minutes, not available for credit notes". The calendar one is "via a connector service, one-way, creates events from bookings, shared calendars not supported". The chat one is "built in, one-way, included on all plans".

They remove the logos for twenty integrations that were really file exports, and move them to a section titled "Import and export files". They add a section for "Planned", with three items and no dates, and a form to request others. They add last-checked dates and an owner.

The next month, support questions about integrations fall by about a third. A prospective customer's assistant, asked whether the product works with the accounting tool, quotes the new entry accurately: two-way for invoices and payments, not credit notes. Clear listing reduced questions, and also made the product easier to describe.

Questions makers ask

Is a longer list better? Only if each entry is true and clear. A short, honest list beats a long, vague one.

Should I show integrations I have not tested recently? Retest, or mark the last-checked date and caveat.

What about integrations that are very new? Label them beta, and say what is not yet covered.

How do I deal with requests for something I will not build? Say so, politely, and point to the open interface or a connector service.

Summary

A logo wall says little. List each integration with its name, what it does, direction, type, coverage and limits, setup, status, support and cost. Be honest about whether it is built in, via a connector, via the open interface, manual or community-built. Organise by category, link to documentation, label planned items separately and keep the list reviewed and dated. Write the facts in text so that people and machines can read them, and take care with other companies' names and logos.

Questions and answers

What should an integrations list include?
For each connection: the tool's name, what the integration does, the direction of data, any limits and how to set it up.
Is a wall of logos enough?
No. Logos say nothing about depth, direction or limits, and can imply support that does not exist.
How do I show the difference between a native integration and a workaround?
Label each entry with its type, such as built-in, via a connector service or via the open interface.
Should I list planned integrations?
Only in a separate, clearly labelled section, with no implication that they are available now.
How often should the list be reviewed?
Whenever a connection changes, and on a regular schedule, since broken or retired integrations erode trust.

Sources

Related guides

Ask a question