Integrations section examples

An integrations grid shows prospects that a product works with the tools they already use. Our examples show integration tiles for fictional tools with category filters and a request-an-integration link, designed for marketing pages on web and mobile in eight visual styles, each with light and dark themes. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

Integrations grid design tips

Lead with the integrations your audience asks about most, and use category filters once the list grows beyond one screen.
Give each tile a name and a short line on what the integration does, not just a logo.
Keep logo tiles a consistent size with even padding so differently shaped marks look balanced.
End the grid with a request link so missing tools become feedback instead of a reason to leave.

Questions

Should an integrations section use logos only?

Logos are quick to recognise, but adding the tool name and a short description improves clarity and accessibility. Each tile should also link to a page explaining what the integration does and how to set it up, which helps both visitors and search.

How should a long list of integrations be organised?

Group them into categories such as communication, storage and analytics, and offer search or filter chips. Show a curated selection first, with a link or button to view all. This keeps the section short while proving breadth.

Is it worth adding a request an integration link?

Yes. It gives visitors who do not see their tool a constructive next step and gives your team useful demand signals. Keep the form short, asking for the tool name and an optional email for updates when it becomes available.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.