Lorixen.
EN

Building an integrations directory for your SaaS product

Short answer: Build two layers: a directory page that lets prospects filter integrations by category and type, and one page per integration that explains exactly what syncs, in which direction, how to set it up and what the limits are. Label native integrations and Zapier-based connections differently, because buyers treat them differently. Skip pages for integrations you don't really support; a thin page that only repeats a logo damages trust more than a shorter list.

People rarely browse an integrations directory for fun. They arrive with one question, usually "does this work with the tool I already pay for?", and often from a search like "[your product] + Xero integration". The directory answers the first glance. The individual page answers the follow-up questions that decide whether they book a demo or move on.

A worked hypothetical: a booking SaaS with eleven integrations

To make this concrete, picture a fictional UK product called Slotwise: appointment booking software for physiotherapists, beauty salons and tutors. Everything about Slotwise below is invented for illustration.

Slotwise has eleven connections. Four are native, built and maintained by its own team: Google Calendar, Microsoft Outlook calendar, Stripe and Xero. Two are partner-built. The remaining five exist only as Zapier workflows that its support team has tested. Its old integrations page was a grid of eleven logos with no links, and the sales team kept answering the same three questions by email.

Step 1: sort before you design

The team put every integration in a spreadsheet with five columns:

Integration Type Direction Category Who maintains it
Google Calendar Native Two-way Calendars Slotwise
Xero Native One-way (bookings to invoices) Accounting Slotwise
Stripe Native One-way (payments into bookings) Payments Slotwise
Mailchimp Via Zapier One-way (new client to audience) Marketing Customer's own Zap
A CRM tool Partner-built Two-way CRM Partner

This exercise changed the page more than any design work. Two integrations turned out to be half-finished experiments, so they were removed. One "integration" was really a CSV export, so it moved to the help centre.

Step 2: decide what earns its own page

Slotwise gave every native and partner integration its own page, because those are the ones prospects search for by name and the ones with real setup steps. The Zapier connections were grouped on a single "Connect via Zapier" page with tested recipes, rather than five near-identical pages saying "use Zapier".

That choice lines up with Google's guidance on helpful content, which lists warning signs such as producing lots of content mainly to attract search visits and pages that leave readers needing to search again elsewhere. Five pages swapping one app name for another would hit both.

Step 3: write the integration pages

Each native page answered the same questions in the same order, so readers could compare at a glance. The template is below.

Step 4: make the directory filterable

The directory gained category filters (Calendars, Payments, Accounting, Marketing, CRM), a "Native only" toggle and a search box. Each card showed the logo, a one-line description of what syncs, and a type badge.

The integration page template

Use this as a starting skeleton for each integration you genuinely support:

  1. Headline in search language. "Slotwise + Xero integration" matches how people search. Follow it with one sentence saying what it does: "Turn completed appointments into draft Xero invoices."
  2. What syncs, and which way. A short table: data type, direction, how often (instant, every few minutes, nightly). Be precise. "Two-way" means edits in either app update the other; say if it doesn't.
  3. Who it's for. Which plans include it and which customer types use it most.
  4. Setup steps. Five to eight numbered steps with screenshots, ending with "how to check it worked".
  5. Limits and known gaps. Field mappings that don't carry over, rate limits, what happens on disconnect. This section builds more trust than the feature list.
  6. Built by. Your team, a partner, or the customer's own automation. Name a support route for each.
  7. Help links and FAQ. Link to the full help article rather than duplicating it.
  8. One call to action. Start a trial with the integration pre-selected, or book a demo.

If you sell into the Shopify ecosystem too, Shopify's app requirements checklist is a useful reference for listing discipline: it asks developers to list up to six integrations merchants will be most interested in and to avoid listing Shopify itself, other carts (unless you sync with them) or other apps you don't directly integrate with (as of November 2026). The same restraint suits your own site.

Native versus Zapier: say which is which

Zapier's developer documentation separates private integrations, for internal or controlled use, from public ones published in its App Directory. It says public integrations unlock features such as Zap templates and embedding Zapier in your product, and that building and publishing an integration on its platform carries no fee, with users paying for their own Zapier plans (as of November 2026).

That last point matters on your page. A prospect who reads "Mailchimp integration" and later discovers they need a separate automation subscription feels misled. Write "Connect via Zapier (requires a Zapier account)" on the card.

If you do build a public Zapier integration, Zapier documents a Workflow Element, a prebuilt component that can show an embedded, customisable version of its app directory and Zap templates inside your own product. Some SaaS teams use that for the long tail and keep hand-written pages for their top native integrations. Check Zapier's current docs for eligibility before planning around it.

Partner listings and reciprocal pages

When a partner builds the integration, ask them to publish a matching page on their site and link both ways. Agree who updates screenshots when either interface changes, and add a review date to the page footer so stale steps get caught.

FAQ

Should each integration have its own URL?

Yes, for integrations with real setup steps or two-way syncing. Prospects search for them by name and sales can send a direct link. Lightweight connections can share one page.

How do I handle integrations still in beta?

List them with a clear "Beta" badge, state what works today, and offer a way to join the beta. Don't let a beta card look identical to a mature integration.

Do integrations pages help with search?

They can, when each page answers a genuine "X + Y integration" query with specific detail. Pages that differ only by app name add little and may be treated as low-value content.

Who should write the setup steps?

Whoever supports the integration. Have support review the page before launch, then again whenever the feature changes.

Turning a logo wall into a set of integration pages prospects can actually use starts with that spreadsheet, so share your current list and we'll help sort it.

Sources

WhatsAppLet’s talk