Cademy can send customer and training data to Salesforce. This lets your team see contacts, organisations, course dates and registrations alongside the information already held in your customer relationship management (CRM) system.

​

This guide explains what the integration does and takes you through the full setup, one step at a time.

​

A module is one group of records you can sync, such as Contacts, Organisations or Course Dates. The full setup includes Salesforce field and object setup, the Cademy connection and testing. You can start with Contacts and add other modules later.

​

​

You will need:

The Apps menu is shown only to System Admins. If you are a System Admin and cannot see Apps, it has been hidden from your menu: look under More.

​

If you cannot see Salesforce under Apps in Cademy, contact Cademy Support before continuing.

​

​

Cademy starts sending records when they are created or changed after you connect Salesforce and enable the relevant module. It does not send all your existing Cademy records when you first connect.

​

For example:

There is currently no button to send all existing records. The Retry button in Sync Activity is offered only on a row that says Failed.

​

Do not try to force a full sync by making bulk changes to your Cademy records. This can change important dates, trigger other integrations and send too much data to Salesforce at once. If you need historic data moved into Salesforce, contact Cademy Support before connecting.

​

​

Cademy uses its own unique ID fields in Salesforce to recognise records it has synced before. An existing Salesforce Contact or Account will normally have an empty Cademy ID field.

​

This means Cademy may create a new Salesforce record even if a similar Contact or Account already exists. If Salesforce already contains many of the same people or organisations as Cademy, contact Cademy Support before enabling the sync. Agreeing how those records will be matched first helps you avoid duplicates.

​

​

The sync is one-way:

​

Cademy → Salesforce

​

Changes made in Cademy can be sent to Salesforce. Changes made in Salesforce are not sent back to Cademy.

​

Cademy never deletes a record from Salesforce. Turning off a module or disconnecting Salesforce stops future updates, but it does not remove information that has already been sent.

​

Contacts are turned on when you connect. The other modules are off so that you can create their Salesforce fields and check their mappings before any data is sent.

​

Course Date and Registration are custom Salesforce objects. You create them by following the recipes in this guide.

​

Cademy uses the Cademy ID field in Salesforce to find the same record on later syncs. It does not match records by name or email address. This is why the fields must be created before the connection and why similar Salesforce records with an empty Cademy ID field can become duplicates.

​

If you connect more than one Salesforce org, Cademy sends new changes to every connection marked Ready. The Default label identifies your main connection, but it does not stop your other Ready connections from syncing.

​

​

The Client Credentials flow lets Cademy connect to Salesforce without a person signing in each time. It always works as one named Salesforce user, called the execution user for an External Client App. In a Connected App, this setting is labelled Run As. This guide assumes that Salesforce user already exists. If it does not, ask your Salesforce administrator to create a user whose license supports API access.

​

Use a dedicated integration user if your Salesforce plan allows it. This makes the integration easier to audit and prevents it from stopping when a staff member leaves.

​

The user needs:

Do not give this user Delete access just for Cademy. The integration never deletes Salesforce records.

​

You can give the access through a profile or a permission set. A permission set is usually easier to review later.

​

To create a permission set:

Keep the integration user's username nearby. Salesforce may use a username that looks like an email address, but it is not always the same as the user's contact email.

​

​

A production URL normally looks like:

​

https://yourcompany.my.salesforce.com

​

A sandbox or Developer Edition URL may look like:

Use the My Domain URL, not a Lightning page address ending in .lightning.force.com, and do not add /services/oauth2/token to it.

​

​

Create these fields before you add the Salesforce connection in Cademy. The integration checks for them while it creates the starting mappings.

​

Check that the final API name is exactly:

​

Cademy_Contact_ID__c

​

If you plan to sync Organisations now or later, repeat the same process under Object Manager, then Account, then Fields & Relationships, with these values:

Create this field before connecting even if you plan to leave Organisations off at first. Adding it after the connection is created does not automatically add it to that connection's saved setup.

​

These fields are managed by Cademy. Your Salesforce users should not type into or change them.

​

​

You can skip this step if you only want to sync Contacts and Organisations.

​

Complete the Course Date recipe before the Registration recipe because each Registration links to a Course Date.

​

The object's API name must be:

​

Course_Date__c

​

Open Fields & Relationships on the new Course Date object and create each field below.

For the Cademy Course Date ID field:

For Status, choose the option to enter one picklist value per line, then enter:

Cademy currently sends Scheduled for an active course date and Cancelled when a synced course date is deleted. Keep Completed in the picklist so the object is ready for reporting or future use.

​

A tab is optional for the sync, but useful for Salesforce users:

The object's API name must be:

​

Registration__c

​

Open Fields & Relationships on the new Registration object and create each field below.

For each lookup field:

Add a Registration tab in the same way as the Course Date tab if you want users to find these records from the App Launcher.

​

​

Return to the profile or permission set used by the integration user.

​

Give it these object permissions for every module you plan to enable:

Also give the user read and edit access to:

You only need to grant access to the optional objects if you plan to use those modules.

​

If your Salesforce sharing rules restrict which Contacts or Accounts the integration user can see, make sure it can see the records Cademy may need to update. Ask your Salesforce administrator to use the smallest access that still covers the records you want to sync.

​

​

An External Client App gives Cademy permission to call the Salesforce API. It does not give Cademy the integration user's password.

​

Treat its Consumer Secret like a password. Do not put it in an email, ticket or shared document. After you save the connection, Cademy stores the credentials in encrypted form.

​

Salesforce recommends External Client Apps for new integrations. Since Spring ’26, Salesforce restricts creating new Connected Apps. Existing Connected Apps can continue to work. For a new connection, use the External Client App route. Use the Connected App route below only if you are configuring an existing app or Salesforce Support confirms your org can create one. Salesforce menus can differ by edition and release.

​

The execution user must be set to the exact Salesforce username shown under Setup, then Users, then Users. In a Connected App this setting is called Run As. Do not assume the username is the same as the person's contact email address.

​

Do not paste either value into this guide or send it to Cademy Support.

​

Use this route only for an existing Connected App, or after Salesforce Support confirms that your org can create a new one:

Salesforce restricts creating new Connected Apps. Use the External Client App route for a new integration. If you need a Connected App, ask Salesforce Support whether your org can create one.

​

Salesforce says OAuth changes can take a few minutes to become active. If the connection test fails immediately after setup, wait a few minutes and try again before changing the settings.

​

​

Cademy installs the app and opens the Salesforce connections page. Installing the app does not send any data. You still need to add a connection.

​

​

Your first connection becomes the default connection automatically. Saving the connection creates the starting mappings but does not send all your existing records.

​

​

Go to Apps, then Salesforce, and select the connection you have just added. The Mappings page shows one card for each module.

​

Open each module, check its settings and select Save after making a change. Switching a module on does not send old records by itself. From that point, records in that module are sent when they are created or changed, or when another record being synced needs them.

​

Contacts sync to the standard Salesforce Contact object. This module is on by default.

​

Cademy starts with these field mappings:

Cademy uses Cademy_Contact_ID__c to create or update the same Contact each time.

​

If the Cademy contact belongs to an organisation and Organisations sync is on, Cademy makes sure the Salesforce Account exists first, then fills the Contact's Account link. If the Account cannot be synced, Cademy can still sync the Contact without that link.

​

Deleting a contact in Cademy does not delete the Contact in Salesforce.

​

Salesforce normally requires a Last Name when a Contact is created. If your Cademy contacts do not always have one, test the setup carefully and agree a suitable data rule with your Salesforce administrator.

​

Organisations sync to the standard Salesforce Account object. This module is off by default.

​

Cademy starts with this field mapping:

Cademy uses Cademy_Organisation_ID__c to create or update the same Account each time.

​

To turn it on:

Deleting an organisation in Cademy does not delete the Account in Salesforce. Sync Activity keeps a readable message explaining that the Salesforce record was left in place.

​

Course Dates sync to the custom Salesforce Course Date object. This module is off by default.

​

Complete the Course Date recipe in Step 4 before turning it on.

​

Cademy starts with these field mappings:

Cademy uses Cademy_Course_Date_ID__c to create or update the same Course Date each time.

​

To turn it on:

When an active course date is sent, its Status is Scheduled. If a course date that previously synced is deleted in Cademy, Cademy changes its Salesforce Status to Cancelled. It does not delete the Salesforce record.

​

A block groups several sessions into one booking. Each session in a block syncs as its own Course Date. The record for the block as a whole is not synced.

​

Registrations sync to the custom Salesforce Registration object. This module is off by default.

​

Complete the Registration recipe in Step 4 first. Contacts should be on, and Course Dates must be on if you want the Registration linked to its Course Date.

​

Cademy starts with these field mappings:

Cademy uses Cademy_Registration_ID__c to create or update the same Registration each time.

​

The Contact and Course Date lookups are filled automatically, so they do not appear as normal editable mappings. Before writing a Registration, Cademy tries to sync the Contact and Course Date first. If an existing parent record fails to sync to Salesforce, Cademy can still create or update the Registration without that lookup. The parent's own Sync Activity row shows the error. A registration with no Contact or no usable Course Date fails with a readable reason instead.

​

To turn it on:

Registration values work as follows:

Registrations for on-demand or e-learning courses have no Course Date, so they are not synced. The reason appears in Sync Activity.

​

A registration for a whole block has no single Course Date to link to, so it is not synced. The individual sessions can still sync through Course Dates.

​

​

The starting mappings will be enough for many accounts. You can add your own Cademy fields and map them to suitable Salesforce fields.

​

To add a mapping:

You can also remove a mapping using the remove button at the end of its row.

​

If the Cademy field you need does not exist yet, choose Create new field… from the Cademy Field list where that option is available. Create the field, then continue setting up the mapping.

​

Keep these rules in mind:

​

​

Use new test records rather than changing a large number of real records.

​

Test one module at a time:

If a test fails, check Sync Activity before changing your setup. Salesforce's error message will often name the missing permission, required field or validation rule.

​

​

Go to Apps, then Salesforce, select a connection, then select Sync Activity.

​

This page shows up to 100 sync records for that connection, the most recently updated first. Each row is the latest result for one record, not a history.

​

The filter starts on All Statuses, which also shows Not attempted rows. The other filters are:

Each row shows the Cademy record, the Salesforce record ID when available, the last attempt and the latest error.

​

If a row says Failed:

Retry sends that one record again. For a contact, it can also send the contact's organisation. For a registration, it can also send the contact and the course date. This happens only when that module is on and the related record has not synced yet. Only a Failed row has a Retry button.

​

A row that says Needs reconnect has no Retry button, before or after you reconnect. Replace the credentials as explained below. Replacing them does not send that record again and does not change the row. Cademy tries the record again the next time it changes in Cademy, or when another record being synced needs it.

​

While a connection needs reconnecting, changes made in Cademy are not sent to it, and reconnecting does not send them afterwards. Selecting Retry on a Failed row during that time changes the row to Needs reconnect. If a record still needs sending after you reconnect, contact Cademy Support with the record and its status.

​

An on-demand registration or a registration for a whole block appears as Failed with a readable reason. The record for the block as a whole is skipped before a sync attempt, so it does not appear in Sync Activity. The sessions in the block can still sync.

​

​

Salesforce recommends changing OAuth secrets regularly and immediately if a secret may have been exposed.

​

When Salesforce gives you a new Consumer Key or Consumer Secret:

Updating credentials does not remove your mappings.

​

Use Edit Connection for replacement credentials from the same Salesforce org. If you want to connect a different org, use + Add Connection so each org keeps separate mappings and Sync Activity.

​

​

Syncing to that org stops. Existing Contacts, Accounts, Course Dates and Registrations stay in Salesforce.

​

You can reconnect later by choosing Edit Connection and entering valid credentials.

​

​

If you still need help, contact Cademy Support and include:

Do not send your Consumer Key or Consumer Secret. Cademy Support does not need the secret value to investigate a sync problem.

​

​

​

​

I cannot see the Salesforce app in Cademy
The Salesforce feature may not be enabled for your account, or you may not have the System Admin role. Ask a System Admin for your account, or contact Cademy Support.

​

I cannot create an External Client App
Your Salesforce user may not have permission to create External Client Apps. Ask a Salesforce administrator to create it.

​

Salesforce restricts new Connected App creation. Contact Salesforce Support to request access. For a new integration, use the External Client App route if it is available.

​

The connection says invalid client credentials or invalid_grant
Check all of these:

Then return to Cademy and run Test & Continue again.

​

The connection works, but records fail with an access error
The connection test proves that Salesforce can issue a token. It does not prove the integration user can edit every object and field.

​

Check that the Run As user has:

After changing permissions, retry the failed row in Sync Activity.

​

Salesforce says an object or field does not exist
Check the API names, including capitals and underscores. They must exactly match the names in this guide:

Also check the integration user's field-level access.

​

I created a Cademy ID field after connecting
Create the field exactly as shown, then contact Cademy Support before enabling the module. The starting connection setup checks for standard-object ID fields only when the connection is first saved, so adding a field later may not update the saved matching rule automatically.

​

Salesforce rejects a record because a required field is missing
Your Salesforce org may have extra required fields or validation rules that are not part of the starting Cademy mappings.

​

Open the module under Mappings and map a suitable Cademy value to the required Salesforce field. If no suitable value exists, ask your Salesforce administrator whether the rule should have an exception for the integration user. Do not weaken an important business rule without reviewing the effect first.

​

A dropdown value is not accepted
Open the affected mapping and select Map values. Match each Cademy value to an allowed Salesforce picklist value, then save and retry the record.

​

A Contact did not link to an Account
Check that:

Look at both the Organisation and Contact rows in Sync Activity. Cademy can leave the Contact unlinked when the Account cannot be synced.

​

A Registration did not link to its Contact or Course Date
Check that Contacts, Course Dates and Registrations are all enabled and saved. Also check:

Then read the Registration row's error in Sync Activity and retry it after fixing the cause.

​

A course date was cancelled but Salesforce still says Scheduled
Cademy sends Cancelled when a previously synced course date is deleted in Cademy. Check that the Status mapping still points to Status__c. If you removed that mapping, Cademy cannot update the Salesforce status on deletion.

​

I connected Salesforce, but no old records appeared
This is expected. Cademy does not perform a full historic sync when you connect. Records are sent when they are created or changed after setup.

​

Everything now says Needs reconnect
The Consumer Secret may have been changed or deleted, or the Run As user may have been deactivated. Create or copy valid credentials, check the Run As user, then use Edit Connection in Cademy to replace the credentials. Rows that already say Needs reconnect keep that status and have no Retry button. Each one is tried again the next time its Cademy record changes.

​

I changed a field mapping, but old Salesforce records did not change
Mapping changes are used on future syncs. They do not update all old records. The new mapping is used when each Cademy record changes again.