Skip to main content
You’ve built an embedded app for Follow Up Boss. This guide takes the same app into every CRM that runs a marketplace on Rollout, while it keeps running in FUB exactly as it does today. Rollout’s Embedded Apps follow FUB’s model, so most of your app carries over:

How much work it is

That depends on what your app does with the contact:

1. Tell Rollout launches apart

Both FUB and Rollout load your URL with context and signature, so your server needs to know which secret to check against. Rollout keeps any query parameters in your app URL, so register your app with one that marks it:
Register it in the Rollout dashboard, under Embedded apps → Apps. See List your app for the other fields. FUB keeps loading https://app.example.com/crm-panel as before. source only picks the secret. It proves nothing on its own: a launch is from Rollout only if its signature checks out with your Rollout secret.

2. Verify with the right secret

This is server-side code, like your FUB check: it needs your secrets, so it never runs in the browser. It runs when the CRM’s frame requests your app URL, before you render the page. Keep your FUB check, and add a branch for Rollout launches. Your Rollout client secret is your Current secret on the dashboard’s API page. Rollout contexts also carry an expiry and a unique id, so check those too:
Call it from the route that serves your app URL, and render the page only for a launch that checks out:
In Go, Java and C#, verifyLaunch returns the decoded context, and you map it as in step 3. rememberJti is yours to write: it stores each id until its expiry, and fails on one it’s seen. See Verify the context for the details.

3. Map both contexts to one shape

Your app’s code shouldn’t care which CRM it’s in. Turn each context into one shape of your own, and use only that from here on:
In Go, Java or C#, do the same with a struct or record of your own, and your JSON library’s lookups. A few things the mapping takes care of:
  • The contact’s id. FUB’s person.id is the contact’s id in FUB. In a Rollout context, the CRM’s id for the contact is crm.personId. person.id is something else: the contact’s Universal API id, sent only in the case step 5 describes.
  • The workspace. FUB sends account.id. Rollout sends no account id: use org.id, the CRM’s id for the agent’s office, team or site, when the CRM sends one, and the agent otherwise.
  • Ids. FUB’s ids are numbers, unique across FUB. Rollout’s are strings, each CRM’s own, and unique only within one marketplace: two CRMs can both have a contact 1234. Every key above includes x.marketplaceId.
  • Previews. FUB marks a preview with example: true and a debugState. Rollout marks one with x.preview: true, and sends a made-up agent and contact. There are no debug states. See Previews.
The context fields are all listed in Context fields.

4. Key your stored data by source

If your tables store FUB’s ids as they are, a contact 1234 from another CRM would collide with FUB’s contact 1234. Store the keys from step 3 instead, or add a source column:
Do the same wherever you link a CRM user to your own user. FUB apps often match the agent through FUB’s account and user ids. For Rollout launches, link agentKey, which holds the marketplace and user.id, to your user the first time the agent signs in. See Signing agents in.

5. Get the contact’s emails and phones

FUB puts the contact’s emails and phones in the context. Rollout never does. If your app needs them, read them from Rollout’s Universal API:
  1. Ask Rollout to turn on the Universal API for your account, if it isn’t already.
  2. Have each agent connect their CRM account to your app through Rollout Link. This is a one-time step, in your app’s settings or in a popup from your embedded app.
  3. Once their CRM has synced, every launch for that agent carries the contact’s Universal API id as person.id. Fetch the contact with it:
The Universal API’s emails and phones have the same shape as FUB’s context: value, type, status and isPrimary, so code that reads FUB’s can read these. Rollout sends person.id only when the agent’s connection is live, has synced the contact, and the CRM’s connector can match the contact’s id. A contact created moments ago may not have one until the next sync. Until then, show what you can without the email or phone, or ask the agent to connect. If you can’t use the Universal API, build the Rollout side of your app around crmContactId: store your data against it, and ask the agent for an email or phone when your app needs one.

6. Read and write the CRM through the Universal API

If your app calls FUB’s API, for example to add a note or read the contact’s tasks, keep calling it for FUB launches. For Rollout launches, call the Universal CRM API instead, with the credential the agent connected in step 5. It mirrors FUB’s API: the same resources, payloads and responses for people, notes, tasks and more, whichever CRM the agent uses. Have a Follow Up Boss integration? Start here shows how to route those calls by CRM. Don’t write to a CRM on a preview.

7. Let Rollout frame your page

Your page now also loads in a frame Rollout serves, inside the CRM’s page.
  • Framing. You already send no X-Frame-Options, as FUB requires. If you send a Content-Security-Policy with frame-ancestors, add https://universal.rollout.com, the origin of each CRM page your app shows on, and https://dashboard.universal.rollout.com for previews. If you serve the Rollout URL from a new route, check that your framework doesn’t add X-Frame-Options to it. See Let Rollout frame your page.
  • The script. FUB’s embeddedApps-v1.0.0.js works as is. Rollout’s https://universal.rollout.com/api/embedded-apps/app-v1.js does the same, and adds reload(), which reloads your frame with a fresh context, for example after the agent connects their CRM in a popup. If your CSP limits script-src, allow the one you load.
  • Downloads. FUB’s iframe allows downloads. Rollout’s doesn’t: open a popup for them.
See Build the page for sizing, sign-in and the iframe’s limits.

8. Test and list

  1. On your app’s page under Embedded apps → Apps, choose Test the signature check. Open the signed sample, and check that your app takes the Rollout branch and shows a preview.
  2. Submit your app to CRMs’ marketplaces from Embedded apps → Marketplaces. Each CRM reviews it in a preview, so show sample data there, not a sign-in screen. See List your app.

Field by field