Integrations Hub Diagram

About this block

Integrations Hub Diagram tells the architecture story. Copy and a CTA sit beside a bordered panel where four source tools flow into a filled Acme hub through solid curved lines, and three outputs, attribution, audiences, and alerts, flow back out through dashed primary lines. A caption decodes the two line styles, so the diagram reads correctly without color alone.

The sources are an array of icon and label, the outputs a string array, and the curves are two small inline SVGs whose paths fan from the hub. The in and out distinction is the persuasive core, most integration sections only show data arriving, this one shows the product paying rent back to the stack.

When to use

Reach for this block when the objection is another tool that takes and never gives. The return flow answers it structurally, which neither integrations-grid-tiles nor a logo wall can. It suits data products especially, anything whose pitch is we make your existing tools smarter. Use the grid tiles when breadth matters more than architecture.

A natural flow around it on a Marketing Pro page:

Before

• Features explaining what Acme computes between the in and the out

After

• Integrations grid for the full breadth behind the four examples
• CTAs once the architecture lands

What you can display

One strong use is a marketing data hub with enrichment flowing back. Other hubs:

• Reverse ETL. Warehouse in the sources, every business tool in the outputs, with the hub as the sync engine.
• Support copilot. Tickets and docs flowing in, draft replies and tags flowing back to the helpdesk.
• Security platform. Logs in, alerts and posture scores back to chat and ticketing.

Tip: keep outputs to three and name them as nouns the buyer already wants, the diagram sells the return flow, not the plumbing.