What a SaaS integrations page should include

What are the steps

1. Headline with the count or the jobOkta leads with more than 8,000 ready-to-use, pre-built integrations.
2. Search right under itXero lets people search apps, industries and tasks from the hero.
3. Popular integrations firstClose opens with the integrations most teams set up first.
4. One line per cardSay what the integration does, like Calendly bookings syncing into Close.
5. A path for missing toolsAshby adds Open API docs and a Submit Request button.

How do the options compare

Where do these numbers come from

1. Okta Integration Network

Which real examples show it

Okta

1. Lead with the size of the network

A big, exact count answers the buyer's first worry, will it work with my tools, before they type a single search.

1. Put your integration count in the headline
2. Show the exact live number next to the list
3. Tag each card with what it supports

Full breakdown · Source

Xero

2. Sort apps by the job to be done

Small business owners think in tasks, not app names, so job named categories get them to the right app in one click.

1. Name categories after the task, not the tech
2. Let search take tasks and industries
3. Show ratings on every card

Full breakdown · Source

Close

3. Show the integrations teams set up first

New users want to copy what working teams do, so a short list of first setups beats an alphabetical wall.

1. Find the integrations most customers add first
2. Show them in their own row at the top
3. Give each one a single line of what it does

Full breakdown · Source

lemlist

4. Tag the integrations that sync both ways

Sales teams worry about data drifting between tools, so a two way tag answers that before they ask.

1. Describe what moves in and what moves out
2. Tag deep integrations with how they sync
3. Group cards by where people work

Full breakdown · Source

Ashby

5. Give a path for the missing integration

A buyer who cannot find their tool still has a next step, so a missing integration becomes a conversation instead of a lost deal.

1. Add a request button to the directory
2. Link the API docs from the hero
3. Say missing tools may be in the works

Full breakdown · Source

Productboard

6. Draw how data flows in and out

One picture shows where Productboard sits in the stack, so a reader sees the whole workflow before reading a single card.

1. Draw your tool in the middle of the stack
2. Put inputs on one side and outputs on the other
3. Use the same groups as page sections

Full breakdown · Source

What else do people ask

Related answers