Salesforce Integration

Updated 21 Oct 2026 by Haydn

The Salesforce integration keeps your partner programme and your Salesforce org in step. Journeybee leads, deals, partners and partner contacts sync to Salesforce Leads, Contacts, Accounts and Opportunities, and changes made in Salesforce flow back. Everything is driven by your own field mapping, so you decide exactly which Salesforce objects and fields are involved.

Where to find it: Go to Settings, then Integrations. Salesforce sits under the CRM section.

Who can use this: Connecting and configuring the integration is admin-only. Once it is connected, anyone on your team sees the Salesforce links and linked opportunities on leads, deals, partners and contacts.

Before you start

You need a Salesforce user with API access and permission to read and write the objects you want to sync (Lead, Contact, Account, Opportunity). The connection runs as that user, so anything they cannot see or edit will not sync.
Have your Salesforce URL to hand if you use a My Domain or a sandbox, for example https://acme.my.salesforce.com or https://acme--sandbox.sandbox.my.salesforce.com. You can paste a Lightning URL, because Journeybee converts it to the matching login host automatically.
You will be asked to install the Journeybee managed package into your org as part of connecting. It adds the identifier fields Journeybee uses to link records, so the install is required.
Set up your partner stages, deal stages and custom fields first. The configuration screen maps against whatever exists at the time, and re-opening the page picks up anything you add later. See Stages and Custom Fields.

Connecting Salesforce

Go to Settings, then Integrations, and click the Salesforce card.
Optionally fill in Salesforce URL. Leave it empty to use the standard Salesforce login; enter your My Domain or sandbox URL to connect that org instead. Only Salesforce addresses are accepted, and anything else falls back to the standard login host.
Click Connect. You are sent to Salesforce to authorise Journeybee. Sign in with the user the integration should run as.
After you authorise, Salesforce opens the package install screen for the Journeybee managed package. Install it for the users who need it. The package adds the Journeybee identifier fields to Lead, Contact, Account and Opportunity, and these hold the link between each Salesforce record and its Journeybee record, so do not delete or restrict them.
Back in Journeybee, open the Salesforce card under Settings, then Integrations, and go to Configure to set up your mapping. Nothing syncs until you do.

The configuration screen

The Salesforce configuration page has four areas in its sidebar:

Integration: the connection itself, plus Remove Integration if you ever need to disconnect.
Configure: all sync settings, field mappings and stage mappings, grouped into sections.
Import: load records from Salesforce and bring partners or deals into Journeybee.
Manage: back to all integrations.

Each section shows a status of Not configured, Configured or Changes pending, and mapping sections show how many of their mappings are complete. Use the search box, the Only unmapped filter and Auto-match, which fills in every field that has exactly one matching Salesforce field, to work through a long list, then save. Changes apply to future sync activity, not retrospectively.

Partner sync settings

This section tells Journeybee how to recognise a partner in Salesforce and how to avoid creating duplicates.

Select the Account field that identifies a partner in Salesforce: pick a picklist or checkbox field on Account and the value that marks partner accounts, for example Type = Partner.
Account unique field for matching: set per partner type, including distributor. Pair a Journeybee partner field with a Salesforce Account field so an existing account is matched instead of duplicated.
Select a unique Salesforce Contact field to prevent duplicate Partner Contacts from being created: pair Email, First Name, Last Name or Phone Number with the equivalent Contact field.
Should we create a new Salesforce Account as a Partner if we don't find one? Choose Yes to have Journeybee create the account when no match is found, or No to leave it alone.
Create partner in Salesforce once it reaches stage: set separately for referral and reseller partners, and only shown for a partner type that has at least one active partner stage. Pick a Journeybee partner stage and new partners are only created in Salesforce once they reach that stage or a later one. Leave it blank to create them as soon as they sync. This only affects creation; partners already linked to a Salesforce Account keep updating whatever their stage.
When a Salesforce partner Account already exists and When a Salesforce partner Contact already exists: how Journeybee treats the partner fields you map when it updates a record already in Salesforce — Two-way: Journeybee updates Salesforce (the default), Salesforce wins: Journeybee only fills blank fields, or Salesforce only: Journeybee never updates existing records. The matching lead and deal settings below explain what each choice does.

Automatic partner import

The Automatic Partner Import settings, also in this section, let Journeybee bring in partner accounts from Salesforce on its own, using the Salesforce Account field and value you set under Partner Import Settings.

Automatically import new partner accounts from Salesforce: off by default. When on, every 15 minutes Journeybee looks for matching Accounts that are not yet linked to a Journeybee partner. Each one is linked to an existing partner when its website domain or name matches, or otherwise created as a new offline partner with its Salesforce contacts. No portal invitations are sent. An Account with no Contact that has an email address is skipped, so add one in Salesforce or import that partner manually.
Salesforce Account field for partner type: choose an Account picklist field, then map a value to each of your partner types (Partner type: Referral, Partner type: Reseller and so on). Imported Accounts get the partner type their value maps to. An Account with no matching value uses the fallback Partner Type from the Import settings.

Lead and deal sync settings

One-way creation sync to Salesforce: new Journeybee leads and deals create records in Salesforce, but later Journeybee edits do not change them. Salesforce changes still sync back. Notes are not affected.
Only create the Account, Contact and Opportunity after the Salesforce Lead is accepted: Journeybee creates only the Salesforce Lead and waits until someone converts it in Salesforce before creating or linking the Contact, Account and Opportunity. After conversion it updates the records Salesforce created rather than making new ones.
Auto-approve leads with no open Salesforce opportunity: off by default. When on, every new lead is checked against Salesforce for an open Opportunity on the matching Account or Contact (and on a converted Salesforce Lead). If none is found — including when the lookups run and the lead matches no Salesforce Account, Contact or Lead at all — the lead is set to Accepted automatically and synced according to your other lead sync settings. If an open opportunity is found, or the check cannot run (for example the lead has no email or mapped unique-field value to match on), the lead stays New, is not sent to Salesforce, shows a Held for review banner listing the open opportunities, and the lead's assigned users and partner managers receive the Lead needs review notification. Setting the Lead Status to Accepted or Rejected ends the hold. Sent referrals and campaign leads are never checked, and partners are not told that a matching opportunity exists. See Notifications.
Sync sent-referral leads with Salesforce and Sync sent-referral deals with Salesforce: both off by default. Leads and deals you have sent out to a partner stay out of Salesforce unless you turn these on.
Auto-create leads from partner associations in Salesforce: a Salesforce Lead that has a partner account in your configured Lead partner association field creates a lead in Journeybee, even if nothing was linked before. Requires the Lead partner association to be mapped.
Auto-create deals from partner associations in Salesforce: the same for Opportunities associated with a known partner, where Journeybee creates the lead and the deal. Requires the Opportunity partner association to be mapped.
Show account owner to partners: off by default. When on, partners see a read-only Account owner block on their leads and deals in the partner portal, listing the record owner's name, title, photo and email. The CRM is never named to the partner, and reassigning the owner stays in Journeybee.
Choose how the integration should interact with existing objects: Link to existing objects, Link to existing objects with no attached partner, or Do not link to existing objects. This governs whether a match on your unique fields is adopted or a new record is created.
Unique field for matching: set per partner type for Contact, Account, Lead and Opportunity, pairing a Journeybee field with a Salesforce field.
Sync on Lead Status: restrict sync to leads with the statuses you tick (New, Accepted, Rejected). Deals follow their lead's status. Leave it empty to sync every status.
Lead note sync direction and Deal note sync direction: Journeybee to Salesforce only (the default), or do not sync notes.
When a Salesforce Account already exists, When a Salesforce Contact already exists, When a Salesforce Lead already exists and When a Salesforce Opportunity already exists: one setting per object, deciding what Journeybee does with the fields you map when it updates a record already in Salesforce. Two-way: Journeybee updates Salesforce is the default and keeps the usual behaviour. Salesforce wins: Journeybee only fills blank fields writes the Journeybee value only when the Salesforce field is empty. Salesforce only: Journeybee never updates existing records leaves the field to Salesforce. Under either Salesforce-first choice, the Salesforce value is also copied back onto the Journeybee record within seconds. Records Journeybee creates always get every mapped field, and Salesforce changes keep syncing into Journeybee in every mode. Override any single field with the Update behavior dropdown on its mapping row — see Field mapping.

Field mapping

Field mapping is what actually turns sync on. A Salesforce object is only created or updated if you have mapped at least one field for it, so map only the objects you want involved.

Each row also shows an Update behavior dropdown once a Salesforce field is picked, which overrides the object's setting for that field alone: Use default follows the When a Salesforce … already exists setting, while Two-way, Salesforce wins (fill blanks) and Salesforce only give the field its own rule. Submitted By has no dropdown and is always written.

Salesforce Partner Fields: Journeybee partners to fields on the partner Account. Changes to a mapped Company Name, Website, Company Email, Company Phone or Company Description in Salesforce also update the partner in Journeybee; an empty value in Salesforce leaves the Journeybee value as it is. A partner's Primary Domain is sent to Salesforce but never changed from Salesforce, because it controls portal access.
Salesforce Partner Contact Fields: partner contacts to Contact fields, being First Name, Last Name, Email, Phone Number and Position/Job Title.
Salesforce Contact Fields and Salesforce Account Fields: Journeybee lead details to the prospect's Contact and Account. The lead's Company Name is offered on the Account and Salesforce Lead mappings only — it is never written to the Contact.
Salesforce Lead Fields: Journeybee lead details to the Salesforce Lead object.
Salesforce Opportunity Fields: deal name, deal value, commission value, expiration date and deal custom fields.
Submitted By: offered on all four object mappings — Contact, Account, Lead and Opportunity. It writes the name and email of the Journeybee user who submitted the lead or deal into a Salesforce text field, so your team can see where the record came from. It only flows out to Salesforce and is never read back or cleared.

Custom fields appear alongside the standard ones, filtered to the partner types they belong to, and only Salesforce fields of a compatible type (and that your connected user can write to) are offered. Multi-select custom fields pair with Salesforce multi-select picklists (or a text field). Every selected option is synced; when values come in from Salesforce, options that do not exist on the Journeybee field are left out and the rest are kept.

Summary note

Each synced Salesforce record can carry one summary note written by Journeybee, so your team can review a submission at a glance without leaving Salesforce. A Summary Note section sits at the bottom of the Contacts, Accounts, Leads and Opportunities tabs on the configuration page, each with its own toggle — off by default — and its own checklist of fields.

Turn on Add a summary note to Salesforce Contact records — or the equivalent on the Account, Leads or Opportunities tab — and tick the fields to include under Lead fields in the summary note (on the Contact, Account and Leads tabs) or Deal fields in the summary note (on the Opportunities tab). Standard and custom fields of any type can be included, including long text.
Each record gets its note the next time it syncs to Salesforce: a Salesforce note linked to that record only, listing each chosen field as a label and value. Empty fields are left out.
The note is created on the first sync and written again only when its content changes. A note deleted in Salesforce is recreated on the next sync.
Summary notes flow from Journeybee to Salesforce only.

Status and stage mapping

Salesforce Partner Stages: choose an Account picklist field, then map each Journeybee partner stage to one of its values. Referral and reseller partner stages can be mapped; distributor partner stages are not synced with Salesforce.
Salesforce Lead Status: map New, Accepted and Rejected to your Salesforce Lead statuses. You can select more than one Salesforce status for each Journeybee status; any of them coming in from Salesforce sets that Journeybee status, and the first one you selected is the status written back to Salesforce. There is also a special Converted (Lead was converted in SF) option, so a lead converted natively in Salesforce marks the Journeybee lead as accepted.
Salesforce Opportunity Stages: map each Journeybee deal stage, per partner type, to an Opportunity stage.
Stage safety: if Journeybee cannot read the opportunity's current stage in Salesforce, it leaves the stage untouched while the other fields still sync.

Partner associations

These settings write the partner on to the synced Salesforce records so your team can see where a deal came from. Each is optional:

Account, Lead and Opportunity Partner Association: the field on that object that holds the partner account's record ID.
Account, Lead and Opportunity Partner Contact Association: the field that holds a contact ID. Journeybee links the partnership's primary contact.
Salesforce Opportunity Distributor Association: shown only when distribution partnerships are enabled for your account. Choose an Account lookup field on the Opportunity that holds the deal's connected distributor. Journeybee writes the distributor's account into it, and when a deal is created or updated from Salesforce the distributor named there is set on the deal, as long as that account is a distribution partner already linked to the deal's partner in Journeybee. An empty lookup never removes a distributor, and a distributor on its own never creates a deal: the partner association must resolve first. See Distribution Management.

Co-selling partner sync

Before you turn it on

Turn on Co-selling under Settings, then Platform Modules.
Create your supporting partner roles (and, if you want to sync it, your primary partner roles) on the Co-selling roles tab under Categories & Tiers. The sync maps Salesforce values to these roles, so add them first.
Make sure each partner Account in Salesforce is linked to its Journeybee partner, either by importing it or through the Journeybee fields on the Account. A record that points at an Account not linked to a partner is skipped until that record, or its Opportunity, next changes.

With the Co-selling module on (see Platform Modules), the configuration page gains a Co-selling Partners section under Opportunities. Turning on Sync co-selling partners keeps every partner on a deal in step with Salesforce, both ways — a partner added, removed or given a new role on either side is matched on the other. It covers the deal's supporting partners and, optionally, the primary partner's role; the primary partner itself keeps syncing through the Opportunity partner association as before.

Partner sources: where Salesforce keeps an Opportunity's partners — up to 10, in priority order, each built with Add source. If a partner appears in more than one source, the first source sets its role. Each source is one of two kinds under Where the partner is:
- Opportunity lookup field: an Account lookup field on the Opportunity itself — one partner per field.
- Related object: any Salesforce object, standard or custom, that has a lookup to the Opportunity and a lookup to the Account — for example a Partner Influence object. Pick the Object, its Opportunity field and its Partner field.
Partner role: the role partners from that source get on the deal — either Same role for every partner, set per partner type, or Role from a picklist, which maps each picklist value to one of your supporting partner roles. A value you do not map gives the partner no role, and where several values map to one role the first is written to Salesforce. Roles are set up per partner type in your partner settings.
Primary partner role: optional — also sync the role of the deal's primary partner, read from An Opportunity picklist or from The primary partner's related record (a related-object source whose role comes from a picklist). It only ever updates the role on the deal; it never creates one.

Set it up

Go to Settings, then Integrations, open Salesforce and go to Configure.
Open the Opportunities tab and choose the Co-selling Partners section.
Turn on Sync co-selling partners.
Click Add source. Under Where the partner is, choose Opportunity lookup field or Related object. For a lookup field, pick the Account lookup on the Opportunity. For a related object, pick the Object, then its Opportunity field and its Partner field.
Under Partner role, choose Same role for every partner and pick a role for each partner type, or choose Role from a picklist, pick the Picklist field, and choose which values give which role. If the picklist fields are not listed yet, save the source once to load them. A value you do not map gives the partner no role.
Repeat for any other place Salesforce keeps partners, up to 10 sources. Use Move up and Move down to set the priority: if a partner is in more than one source, the first source sets its role.
Optional: under Primary partner role, set Read the role from to An Opportunity picklist or The primary partner's related record if you also want the primary partner's role synced.
Save. A source that is not finished shows Finish this source to save your changes.

Journeybee changes reach Salesforce within seconds; Salesforce changes arrive on the same 15-minute cycle as the rest of the integration, and switching the sync on backfills from your oldest Salesforce records, so a large org catches up over several runs. A partner removed in Journeybee deletes its Salesforce record or clears the lookup — but only records still pointing at that partner's own Account, so a record since pointed at another Account is left alone. A record deleted in Salesforce, or a lookup cleared there, detaches the partner in Journeybee. Archiving or deleting a partner in Journeybee never deletes Salesforce data.

The connected Salesforce user needs to read and write every object and field used as a source, and to see every record of a related-object source — a record it cannot see reads as removed and detaches the partner. Problems the integration cannot resolve appear under Sync issues on the configuration page: a source that can no longer be read is paused until it reads again, and a role that no configured source can hold is reported against the deal.

What the Salesforce user needs

The connected Salesforce user needs:

Read, create, edit and delete access to each related object used as a source.
Access to see every record of those objects (through sharing rules or View All). A record the user cannot see looks removed, and its partner is detached from the deal.
Field-level edit access to the lookup and picklist fields you chose.

Limits

A deal shows up to 20 supporting partners. Records beyond that are skipped.
Changing a source or a role mapping applies to future changes. Partners already synced through the old setting are left as they are.
Salesforce changes arrive every 15 minutes, so a large org can take several runs to catch up after you turn the sync on.
If you turn the sync off and back on, changes made on either side in the meantime are reconciled the next time each deal changes.

Troubleshooting co-selling sync

A partner did not appear on the deal. Check the Salesforce Account is linked to a Journeybee partner and is the same partner type as the deal's partner, and that the deal has fewer than 20 supporting partners.
A partner was removed from the deal unexpectedly. The Salesforce user probably cannot see the record any more, or the record or lookup was cleared in Salesforce. Removals sync both ways.
A partner has no role. The Salesforce value is not mapped to a role, or the role is not in the source's mapping. Add it to the mapping, and the deal updates the next time it changes.
A source shows under Sync issues. Its object or one of its fields cannot be read, so partners from that source are paused until it reads again. Check the object and field access for the Salesforce user.

See Co-selling for how supporting partners work across Journeybee.

What syncs and when

Journeybee to Salesforce happens within seconds of a change. Rapid edits are batched into a single write, so you get one clean update rather than a burst.
Salesforce to Journeybee runs on a schedule, every 15 minutes. Each run picks up Salesforce records changed since the last run that carry a Journeybee identifier field, plus any records caught by the auto-create settings.
Notes sync one way, from Journeybee to Salesforce. A note is attached to the Salesforce record as a file called Journeybee Note.
Auto-create is capped per run, at up to 500 leads and 50 deals, so a large backfill catches up over several runs rather than in one go.
Unmapped Opportunity stages: once you have mapped any Opportunity stages, a Salesforce Opportunity in a stage you have not mapped does not create a new deal in Journeybee. A deal that already exists keeps its current Journeybee stage. Map every stage you want to see as a deal.
No echo back to Salesforce: when a Salesforce record creates something in Journeybee — through an import, an auto-create run or a scheduled sync — Journeybee does not update that Salesforce record. The only writes are the Journeybee identifier fields and, on a new opportunity, the link to the partner's account, which keep the records linked. Those writes can still trigger Salesforce automations such as flows, so exclude the Journeybee fields from any trigger that should not react to an import or sync.
Salesforce-first fields pull back straight away: when a field is set to Salesforce wins or Salesforce only and Salesforce holds a value, that value lands on the Journeybee lead, partner, partner contact or deal within seconds rather than on the next scheduled run — a pulled-back deal value recalculates commission too. Under Salesforce wins, a Salesforce field left blank also stops clearing the Journeybee value on the 15-minute pull.

Importing existing Salesforce data

Partners

In Partner Import Settings, pick the Salesforce Account field and value that identifies your partners. For a checkbox field, choose True or False. Then choose the Partner Type on the same screen. If you have mapped a Salesforce Account field for partner type under Automatic Partner Import, each account gets the type its value maps to, and this Partner Type is the fallback for accounts with no matching value.
Open the Import tab and click Load records. Journeybee lists the matching accounts on the Partners tab, 50 per page, with their Salesforce contacts underneath. Use Search by name to find an account, the page controls to move through the list, and Select all on this page to tick a whole page. Your selections stay in place as you page, search and switch tabs.
Click Import in the bar at the bottom — it counts the partners, contacts and deals you picked. Each account becomes a Journeybee partner, with its selected Salesforce contacts added as partner contacts and the Salesforce IDs stored so future changes stay linked. The page reports the import's progress until it completes. Accounts and contacts already linked to Journeybee are marked as imported, and you can still select an imported account to bring in its remaining contacts.

Imported partners are created as offline partners, so no portal invitation is sent. Invite them from the partner page when you are ready. See Partner Contacts.

Deals

Map your Opportunity stages first, so imported deals land in the right pipeline stage.
On the Deals tab (Partners to Import Deals For), each partner lists its unimported opportunities by name. Tick the opportunities you want to bring in, or tick the partner to select all of them. Opportunities already imported, and partners with no new opportunities, are not shown.
Click Import in the bar at the bottom to run the import. Journeybee creates a lead and deal for each selected opportunity, and marks the lead as accepted. Deals that already exist but are missing their link fields are repaired rather than duplicated. An opportunity whose Salesforce stage is not one you have mapped is skipped, so map every stage you expect to import. If you have mapped no Opportunity stages at all, deals are imported on your default Journeybee stages instead. An import sends no lead or deal notifications — the records simply appear.

Only one deal import can run at a time per connection, and your selection is cleared when the import starts so a retry never re-imports the same opportunities.

A deal imported straight into a won or lost stage is dated by the opportunity's close date in reports, not the day you imported it — so historical deals land in the period they actually closed. This applies to new imports only; deals brought in earlier keep their import date.

While a partner or deal import runs, the workspace shows its status — Queued, then Running with a percentage, then Completed — and reports how many selections were processed. When it finishes, the lists refresh so imported records are marked and no longer offered. If the lists cannot be refreshed, a notice explains that the records could not be loaded, and Refresh records reloads them without running the import again.

Working with Salesforce from Journeybee

Open in Salesforce: leads, deals, partners and contacts show a Salesforce link that takes you straight to the matching record in your org.
Salesforce owner: a lead or deal shows the owner of its Salesforce record, and you can search your Salesforce users and set the owner without leaving Journeybee.
Held for review: with Auto-approve leads with no open Salesforce opportunity turned on, a new lead that matches an open Salesforce Opportunity shows an amber banner at the top of the lead panel listing each opportunity with its stage, amount and owner. Click an opportunity to open it in Salesforce, then set the Lead Status to Accepted or Rejected. The banner disappears once the status changes.
Linked opportunities: a lead lists the opportunities on its Salesforce account or contact and marks the ones already connected. Use Create deal from CRM to link an existing opportunity, and Journeybee stamps the lead on to it and pulls it in as a deal on the next sync.

Sync issues

When a write to Salesforce fails — because a stored link no longer works, for example the linked record was deleted in Salesforce or the connected user cannot access it, or because Salesforce refuses the write itself, such as a validation rule failing or a required field being empty — Journeybee reports it under Sync issues on the Salesforce configuration page. The panel sits between Reconnect and Disconnect integration and only appears while there is something open, so a healthy integration shows nothing.

Each entry names the Journeybee record and what went wrong. Depending on the issue, you can:

Relink partner: pick the Salesforce Account the partner should sync to. Open deals on the partner re-sync automatically afterwards.
Clear link: remove the stored Salesforce link from the record, so the next sync can link or create it again.
Link to matched record: adopt the existing Salesforce record Journeybee found but could not safely link on its own.
Retry sync: re-run the sync for that lead or deal straight away.
Retry all: on a rejected group, re-run the sync for every record it covers — leads, deals, partners and partner contacts.
Dismiss: close a settings warning you have decided not to act on.

When Salesforce refuses a write outright — for example a validation rule fails, a required field is empty, or a value is not among a field's allowed options — every record refused for the same reason is grouped into one entry, such as "Salesforce rejected 18 leads: Channel Source Is Mandatory". The entry tells you what to fix, and Show records lists the affected records. Once the cause is fixed, Retry all re-runs the sync for the whole group, up to 200 records at a time; a record can only be retried once every 5 minutes, and one that has since been deleted or archived in Journeybee is cleared instead of retried. The issue closes itself once a write to that record succeeds.

The panel also flags settings problems, such as a partner association field that is no longer valid, and warns when partner matching is on but an object has no partner field set, because existing records are then linked regardless of partner. An entry saying Salesforce rejected a field means a mapped field refused its value and was left out of the last sync — check the field mapping and the value in Journeybee; it clears itself once a later sync writes the field. An issue clears itself once a sync to that record succeeds, and fixing one is admin-only, like the rest of the configuration page.

Troubleshooting

Nothing is syncing at all. Check the section you expect to sync actually has field mappings saved. An object with no mapped fields is never created or updated.
A banner says Salesforce needs reconnecting. The connection's refresh token has expired or been revoked, and sync is paused until it is restored. Admins also get an email. Open the Salesforce card under Settings, then Integrations, and connect again. This clears the flag and sync resumes on the next run.
Records are rejected as duplicates. When a Salesforce duplicate rule blocks a create, Journeybee links to the matching record of the same object instead of creating another one. If a match is found but cannot be linked safely, it is listed under Sync issues on the configuration page instead. A cross-object match, such as Salesforce's standard Contacts-versus-Leads rule, cannot be linked, so that record is skipped. Resolve it in Salesforce or adjust the rule.
Writes fail on required fields or validation rules. Salesforce rejects the write if a required field is empty, a validation rule fails, or the connected user lacks access to the field, and the refused records appear grouped under Sync issues on the configuration page. Map the missing field in Journeybee, or relax the rule for the integration user, then use Retry all on the group to re-run them.
Changes in Salesforce take a while to appear. That direction is on a 15-minute cycle. Also check the Salesforce record still has its Journeybee identifier field populated, because clearing it unlinks the record.
A converted Salesforce Lead stopped updating. Once a Lead is converted, Salesforce makes it read-only. Journeybee keeps syncing to the Account, Contact and Opportunity created by the conversion instead.
A new lead says Held for review: the Salesforce check could not run. Journeybee could not confirm whether Salesforce has an open opportunity, for example because the connection needs reconnecting or the lead has no email or mapped unique field to match on. The lead is kept in New and out of Salesforce until you set its Lead Status yourself.
Sent referrals are missing from Salesforce. The two sent-referral toggles are off by default. Turn them on if you manage sent referrals in your own pipeline.
The connection went to the wrong org. Remove the integration and connect again, this time entering your My Domain or sandbox URL on the connect form.

Good to know

Salesforce uses OAuth2. Journeybee stores the connection at company level, so it does not matter who reconnects it later, as long as they are an admin.
Everything is opt-in. A setting you leave blank simply means that behaviour is off: no fields are written and no records are linked by default.
Partner sync covers referral, reseller and distributor partners. Partner stage mapping, partner creation stage thresholds, and lead and deal mapping apply to referral and reseller partner types.
The Journeybee identifier fields added by the managed package are how records stay matched. Keep them on the objects and readable by the connected user.
Removing the integration stops all syncing but leaves your Journeybee records, and the Salesforce records, exactly as they are.
For the other tools you can connect, see Integrations.