Connecting and syncing LinkedIn accounts

Hosted connection

Fulreach attaches LinkedIn outbound through hosted authentication flows mediated by Unipile (Fulreach persists canonical account rows referencing provider payloads after successful onboarding).

Generating a fresh connection issues a Fulreach-hosted UUID account id upfront then exchanges provider callbacks so future API calls correlate workspace membership with Unipile’s live account id.

Hosted setup returns a timed link. Complete it promptly; expired links regenerate from product UI.

List and switch accounts

The web experience lists identities returned from Unipile—payload shapes vary (names, statuses). Fulreach normalises minimally for selectors; statuses may drift until sync.

Sync

Sync pulls upstream LinkedIn account metadata into Fulreach (connected/disconnected flags, timestamps, enriched names). Typical reasons to sync:

• After changing LinkedIn session state externally.
• If campaigns stall with auth-like errors reconnect first then sync confirm.

Upsert merges alias mappings between Fulreach canonical IDs and provider account IDs when multiple LinkedIn devices exist historically.

Reconnect scenarios

Fulreach marks accounts needing attention when OAuth tokens expire—reconnect flows regenerate secure paths without manually storing LinkedIn passwords in Fulreach (handled by hosted provider handshake).

After reconnect, clients land on a public confirmation page (/linkedin/reconnected) and do not need a Fulreach login; operators confirm status in Workspaces.

Operational symptoms:

• Invite/DM pipelines report Disconnected classifications.
• Unipile 401-equivalent classifications show in technical error surfacing (“UNI…” codes); user action is reconnect or wait for provider outages.

Campaign actions always include account_id referencing the chosen LinkedIn context—incorrect selection produces empty candidate pools or unreachable sends until corrected.