Solutions / Use case

Embedded integration, built once and run for every customer.

Embedded integrations are the ones your customers find, connect and set up inside your product, under your brand. With Tray Embedded your team builds each integration once, and every customer runs it with their own accounts and settings.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Jump to the stages
One customer setting up an embedded integration inside a software product: connecting their Salesforce account, matching 14 fields, choosing a Slack channel for alerts and syncing 4,812 contacts, live in minutes with no ticket to engineering.

The short answer

What is embedded integration?

Embedded integration is a software company offering integrations with other apps inside its own product, where customers find them, connect their accounts and set them up on their own, under the company's brand. It runs from choosing which integrations to build, through building each one once for every customer, to the connections, settings, errors, updates and adoption that follow. Most of the work comes after launch, because every customer's integration has to keep working for as long as they use it.

  1. 1 Choose
  2. 2 Build once
  3. 3 Connect
  4. 4 Map and go live
  5. 5 Handle errors
  6. 6 Ship changes
  7. 7 Track adoption
less likely to churn when Podium customers integrate
60%
build time per integration at HackerOne
2–3 months → 2–3 weeks
retention on Cvent's Microsoft Dynamics integration
95%
integration releases a quarter at Bynder
2–3 → 7–8

The embedded integration process, stage by stage

Seven stages, each with what breaks and a how-to guide for building it.

  1. 1

    Choose what to build

    Requests from deals, tickets, feedback and calls are counted once per account and ranked by the revenue behind them.

    Where it breaks: The loudest deal sets the roadmap, and the integration three hundred customers asked for waits.

  2. 2

    Build once for every customer

    One set of workflows holds the logic, and every choice that differs between customers becomes a setting with a default.

    Where it breaks: Each customer gets a copy with their own tweaks, so one fix has to be made four hundred times.

  3. 3

    Customers connect their accounts

    Customers sign in to their own apps inside your product, under your name, and every connection is checked daily.

    Where it breaks: A connection expires on a Saturday, the sync stops without a word, and the customer finds out on Monday.

    Example connections

  4. 4

    Customers map their fields and go live

    Customers pick from their own fields, see a preview of real records, and the first sync runs in small batches.

    Where it breaks: The customer's custom field isn't in the list, so they file a ticket and never finish setup.

  5. 5

    Errors reach whoever can fix them

    Every failed run is caught in one place, and the customer hears about what they can fix before they notice.

    Where it breaks: The sync breaks on Tuesday and the customer finds out from a wrong report the week after.

    Example connections

  6. 6

    Ship changes to every customer

    New versions are tested as a customer, and changes that need the customer's input go out in waves.

    Where it breaks: A new required setting breaks every customer who set up before it existed, on the same afternoon.

  7. 7

    Track adoption and retention

    Integrations running per customer are counted daily, shown on the account, and compared with retention.

    Where it breaks: Nobody can say which customers have an integration running today, so retention claims stay a guess.

Three ways to offer integrations

  • Build each one in house. Full control, and every integration is a project for your engineers, then a maintenance job for as long as customers use it. HackerOne spent two to three months building each one before it moved to Tray.ai.
  • Leave it to third parties. A public marketplace fills up fast, but quality and fixes are out of your hands, and customers blame your product when one breaks.
  • An embedded integration platform. You build each integration once on connectors someone else maintains, and customers set it up inside your product under your brand. This is Tray Embedded: your team owns the experience, Tray runs it for every customer.

The Tray.ai platform behind it

Tray.ai is the enterprise orchestration platform for data and AI. These are the parts of it that run embedded integration.

Intelligent Integration

The iPaaS built for the AI era.

iPaaS Governance

AI governance built in, not bolted together.

The metrics embedded integration moves

What product and partnership teams measure, and which stage each number depends on.

Integration adoption rate
Share of customers with at least one integration running, meaning a successful run in the last week.
What moves it Counting integrations that run rather than ones that were set up, and chasing the ones that stop. How to build integration adoption tracking 
Time to first sync
Minutes from a customer clicking connect to their first records arriving.
What moves it A live list of the customer's own fields, default matches and a first sync that starts with the newest records. How to build customer field mapping 
Setup completion rate
Share of customers who start setting up an integration and finish.
What moves it A sign-in that carries your name, and a permissions check that catches problems while the customer is still there. How to let customers connect their own accounts 
Integration support tickets
Tickets a month about integrations, per hundred customers who use one.
What moves it Telling customers about failures they can fix, with the fix, before they notice. How to build error alerts for customer integrations 
Time to ship a new integration
Days from deciding to build an integration to customers being able to turn it on.
What moves it Building once with settings, rather than per customer, on connectors that are already maintained. How to build one integration for every customer 

Embedded integration connectors

The apps your customers ask to connect, and the tools that run the integrations behind them. Each links to its connector page.

CRM

The integration most software customers ask for first.

Marketing and events

Where customers run campaigns, webinars and events from your product's data.

Support, IT and engineering

Where customers' teams track tickets, incidents and work.

Files and content

Where customers store, buy and share files and images.

Collaboration

Where customers want alerts and updates from your product.

Running your integrations

The tools your own team uses to choose, watch and measure the integrations.

Connections between them

Field mapping, templates and common problems for the pairings embedded integration depends on.

Anything not listed connects through the full connector library, or directly through its API.

Teams running embedded integration on Tray.ai

“Customers who integrate with Podium's platform are 70% more likely to be classified as active and 60% less likely to churn. It's more than night and day.”

— Thomas Mancuso, Director of Product Partnerships, Podium
Read the study

Processes next to embedded integration

These share systems and data with embedded integration without being stages of it.

Platform engineering

How to build an API facade

Give consumers one contract instead of six systems, absorb upstream changes rather than leaking them, and keep the caller identity intact. The prompts.

Platform engineering

How to build webhook fan-out

Acknowledge before you fan out, verify the signature first, retry per consumer, and make replay possible. The Headless prompts that build it.

Customer success

How to build a product usage to CRM sync

Send the three signals that change a conversation, aggregated and labelled, without turning the CRM into an analytics tool. The Headless prompts that build it.

Customer success

How to build customer health signals

Weight the signals that predict churn, keep the categories visible instead of one number, and back-test before anybody trusts it. The prompts that build it.

Data operations

How to build schema change management

Detect a source change before it breaks a model, resolve what depends on it, and tell the owner in time to act. The Headless prompts that build it.

Speaking the same language

Definitions for the terms that come up in this conversation.

iPaaS

Integration Platform as a Service — a cloud-hosted platform for building, running, and managing integrations between applications.

Connector

A pre-built integration between Tray.ai and a specific application — Salesforce, Slack, Snowflake, 700+ others.

Frequently asked questions

How is embedded integration different from integrating our own internal systems?

+

Internal integration connects the apps your own teams use. Embedded integration is part of your product. Your customers set it up, it runs with their accounts, and when it breaks it is your product that looks broken. That changes what matters most, from the logic to the setup screens, the connections and the error messages.

Will customers see Tray inside our product?

+

No. Tray Embedded's setup screens take your own styling, the sign-in can run on your own subdomain, and with your own OAuth app registered for each service the approval screen names your product. Or build your own setup screens and call the API behind them.

Do we have to build our own integrations page?

+

No. Tray provides an integration marketplace app you can deploy and place inside your product, which lists your integrations and lets customers set them up. Many teams start there and replace it with their own page later.

What happens when an app we integrate with changes its API?

+

Tray maintains the connectors, so a change at Salesforce or Zendesk is handled below your integrations. HackerOne cut build time per integration from two or three months to two or three weeks, and stopped maintaining each one by hand.

What if a customer asks for an app Tray has no connector for?

+

Tray connects to any app with an API, so a less common app is built the same way as the rest, with the same settings, connections and error handling.

Do integrations really change retention?

+

At Podium, customers who integrate are 60% less likely to churn and 70% more likely to be classified as active. Integration setup at Podium went from up to 14 days to minutes.

Last reviewed 2 October 2026.

See embedded integration running on your stack.

Walk through your systems and stages with a Tray.ai expert.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Browse the how-to guides