TL;DR
- Buy embedded integration infrastructure when your product must connect and support many customers' CRM and adjacent systems. An internal automation account is not the same multi-tenant product requirement.
- Paragon and Prismatic suit customer-facing integration workflows. Merge suits a unified API/data-model approach. Choose the abstraction that matches your product's required objects, writes and freshness.
- Test custom fields, reconnects, tenant isolation and support visibility before counting connector logos. A connector that cannot represent the customer's object model may still leave substantial engineering work.
- Model production connections and activity, then add onboarding and support. One hundred customers connecting two systems produce 200 connections, not two integrations for billing purposes.
An integration becomes part of your product
A GTM software builder may need to import a customer's accounts, enrich them and write accepted changes back to Salesforce or HubSpot. Each customer has different credentials, custom fields and permissions. The product must explain a broken connection to the customer and support team without exposing another tenant's data.
That makes embedded integration a product capability, not simply an internal workflow. The purchase includes authentication, configuration, execution, monitoring and a customer-facing connection experience. The CRM agent platform guide covers the broader product environment; here the focus is the connection infrastructure inside your own tool.
Define the minimum contract before procurement: supported objects, read/write operations, custom-field mapping, deletions, sync frequency and failure recovery. Decide whether the application needs a normalised common model or each vendor's native semantics. A unified “account” object is convenient until a customer needs a relationship the common model cannot express.
Three platform approaches
| Platform | Main approach | Good fit | Question that can disqualify it |
|---|---|---|---|
| Paragon | Embedded integration infrastructure and workflows | Product-specific integration logic | Can the required connector/custom operation support the exact workflow? |
| Prismatic | Customer-deployed integration instances | Configurable per-customer processes | Can customer configuration and support remain manageable at scale? |
| Merge | Unified API with linked accounts | Consistent access across a supported category | Does the common model preserve the required native fields and writes? |
Paragon
Paragon's integration catalogue includes prebuilt and custom integration paths. Its pricing page offers a custom quote based on connected customer organisations, with Managed Sync, ActionKit and Workflows included in the suite. Asynchronous workflows and synchronous actions remain different usage paths. Evaluate the particular product needed rather than assuming every capability is covered by a single connector licence.
It is relevant when your product requires vendor-specific steps, branching and data movement embedded in its experience. Build a representative account sync and a write-back action. Check how custom operations, connection state and customer-visible errors are handled. A catalogue entry is the start of the fit check, not evidence that every endpoint and custom object is supported.
Choose it when that workflow abstraction removes meaningful implementation work. Avoid it when your product only needs a small stable read-only endpoint and the platform adds unnecessary operating complexity. Obtain a quote covering connected customers, usage, environments, retention and support for the exact infrastructure path.
Prismatic
Prismatic's customer documentation describes customers enabling integration instances through an embedded marketplace or your team deploying them. Its connection documentation distinguishes customer/global and integration-scoped connection models. That is useful when the same connector logic must be configured and supported separately for each customer.
This approach fits a product offering configurable integration processes rather than only a common data endpoint. Decide which settings a customer can edit and which your support team owns. Use customer-scoped connections where the lifecycle requires them, and test whether a connection reused across integrations can be changed safely.
The trade-off is configuration and support complexity. A highly flexible workflow can create many variants your team must understand. The pricing page should be checked against the actual proposal, including customer instances, usage and commercial terms. Choose it when per-customer flexibility is necessary; avoid offering configuration choices that your product cannot reliably support.
Merge
Merge's concepts describe linked accounts, account tokens and synchronised data through a common interface. Its CRM overview documents category-specific API behaviour and per-linked-account limits. This can simplify a product that needs consistent account/contact/deal access across supported CRMs.
The important limitation is the abstraction boundary. Verify every mandatory object, field and write in the current documentation. Preserve native identifiers and understand sync freshness. A normalised response is not necessarily a live provider response at the instant the seller opens the page.
Merge's current unified pricing lists $650 monthly for up to ten production linked accounts, then $65 per additional linked account for that offer. The free allowance is three production linked accounts. Professional uses contract pricing and lists access to custom fields and custom sync frequencies, so the Launch arithmetic below does not price that broader requirement. Choose it when the common model covers the product's needs; do not force an unusual native workflow into the model simply to avoid writing a connector.
Nango and Workato Embedded can be additional candidates where their documented authentication/sync or wider workflow model matches the requirement. They are not ranked here without a like-for-like scope and commercial check. Three well-scoped evaluations are more useful than a long list of loosely adjacent platforms.
Design the customer connection lifecycle
Create the connection under a stable tenant ID. Record provider workspace, granting user, authorised scopes and current status. Keep credentials out of prompts and ordinary logs. A customer switching its CRM workspace should not silently overwrite the old connection while pending jobs still reference it.
Handle expiry and revoked consent as customer-visible states. Provide a reconnect path and stop writes until valid authority returns. Reconnection may change scopes or account identity, so verify the workspace before resuming. Do not repeatedly retry a revoked token as if it were a temporary outage.
Treat schema change as normal operations. A customer can rename a custom field, delete an option or change permissions. Keep field mappings and versions, show the broken requirement and prevent partial writes that leave a misleading success state. Preserve raw provider IDs so support can reconcile the destination.
Build a support view showing connection status, last successful sync, failed object and safe error details. The agent framework guide concerns application logic, while the automation comparison covers internal workflow alternatives. Neither automatically supplies your product's multi-tenant support lifecycle.
A hundred-customer cost model
One hundred customers connecting two systems each produce 200 production connections if the billing unit is per connected system/account. Under the observed Merge self-service offer, the example is $650 plus 190 additional linked accounts at $65: $13,000 monthly. Confirm category, contract and current eligibility; this is published-rate arithmetic, not a negotiated quote.
Other platforms may meter customer instances, tasks or activity differently. If each connection synchronises 5,000 changed records daily, the estate handles one million record changes a day before retries and pagination. Price the actual request/operation count, not just the records, and identify whether initial backfills have a separate usage effect.
Assume onboarding takes one hour per customer and support averages ten minutes per customer monthly. At an assumed $60 per hour, initial onboarding is $6,000 and monthly support $1,000. A platform that reduces those burdens can justify a higher software bill, but do not count savings until the product's connection experience works for your customers.
Use the ABM Account Scoring Template as a sample business contract for the synced account fields. It makes a useful distinction between data the connector must preserve and judgement your own application computes.
Choose by the difficult fixture
Test a standard CRM, one with custom objects, a revoked user, a renamed field, a large backfill and a partially successful write. Verify isolation by trying the wrong tenant reference. The purchasing winner should make those failures supportable, not merely finish the easiest demo.
Choose a workflow-oriented embedded platform when per-customer logic is central. Choose a unified API when its model covers the product's required behaviour. Keep an exit plan for mappings and connection reauthorisation, since moving infrastructure can require customers to reconnect. The integration is part of your product promise, so buy it against that promise.
FAQ
Is an embedded integration platform the same as internal iPaaS?
They can share technology, but embedded use needs customer-specific credentials, configuration and support inside your product. Check the commercial rights and lifecycle features for that use rather than assuming an internal automation subscription permits it.
Does a unified API support every custom CRM field?
Support varies by category, provider and operation. Verify the current common-model and custom-field documentation against your required fixture. A broad connector claim is not enough for a product whose value depends on a particular native relationship or write.
Should we bill customers per connection?
That is a product economics decision. Understand your own connection and activity costs first, then choose a customer price that remains sustainable for heavy users. Do not expose a confusing infrastructure meter unless it helps the customer understand their purchase.
What happens when the granting employee leaves?
The provider grant can fail or need reassignment. Detect the state, notify the appropriate customer administrator and require a valid reconnect. Preserve the tenant mapping and pending-work policy so the new connection does not accidentally act in a different workspace.
