Skip to main content

Setting up a FrontSpin tenant

This section takes one customer from nothing to syncing. Follow it in order — each step depends on the one before.

Where the work happens​

Almost all of it is in Salesforce Setup, not in the EasyCRM portal. You need an administrator login to Salesforce itself.

What you need from FrontSpin first​

Ask whoever runs the FrontSpin account for these. Nothing below works without them.

You needLooks likeUsed for
Tenant ID100142Identifying the FrontSpin account
API keya long secret stringAuthenticating every request
Webhook secretanother secret stringProving an incoming webhook is genuine

Both secrets go into Salesforce once and are never typed again. The API key is held in a Named Credential, so it is injected by the platform and never appears in Apex or in a log.

The order of work​

StepPageRoughly
1The Record Type5 min
2The configuration row5 min
3Permissions10 min
4Fields going out15 min
5Fields coming back10 min
6Webhooks20 min
7Checking it5 min

Steps 4 and 5 are optional at first. A tenant with no field mappings still syncs the standard fields; mappings add your own.

A note on the screenshots​

The screens below are real, with customer names, tenant ids and the org address replaced by example values. Field names, layout and everything you click are untouched.

One thing to decide before step 2​

Are you setting up the only FrontSpin account, or an additional one?

  • The only one — follow this section and ignore Routing entirely. The org stays in its default mode and everything works.
  • An additional one — do this section first anyway, then read Routing, which is about running several tenants at once safely.