How it works
Instead of internal IT, the buyer is a SaaS company. The platform supplies the auth flow end users see inside the product, connectors, a workflow runtime and per-customer configuration and monitoring. The vendor's engineers define integrations once, often as workflows, and each customer switches them on and connects their own accounts.
Example
A field-service app lets each customer connect QuickBooks Online from its settings page. Behind the screen, an embedded integration platform runs the auth, the sync of invoices and the error alerts for every customer.
In integrations
Embedded iPaaS and unified APIs overlap. Embedded iPaaS typically gives you a workflow per platform; a unified API gives you one data model across platforms. Unify Int combines the unified model of the Unify Graph with Unify Connect for white-label auth and Workflows for logic that does not belong in your code. The choice depends on how similar your integrations are. If many platforms serve the same purpose, a unified model saves repeated work. If each integration is a bespoke workflow, per-platform tooling may fit better.