BusyBot
Search all guides

Reference · Credentials

Connect LinkedIn to BusyBot

Used by 1 BusyBot node.

Type linkedInOAuth2 6 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes —
Refresh Token
refreshToken		 password No OAuth2 refresh token used to renew the access token after expiry (~60 days).
Client ID
clientId		 string No LinkedIn App Client ID (required for automatic token refresh).
Client Secret
clientSecret		 password No LinkedIn App Client Secret (required for automatic token refresh).
Expires At
expiresAt		 number No Unix timestamp (ms) when the access token expires. Auto-managed.
Person URN
personUrn		 string No Default LinkedIn person URN (e.g. urn:li:person:xxxxx) used as author when post param is empty.

Setting up LinkedIn OAuth2

  1. In LinkedIn OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own LinkedIn OAuth2 account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose LinkedIn OAuth2.
  3. Paste each value into the matching field and save.
  4. Add the LinkedIn node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use LinkedIn credentials?

One node: LinkedIn. Create the credential once and select it in that node.

What does a LinkedIn credential need?

6 fields: Access Token, Refresh Token, Client ID, Client Secret, Expires At, Person URN. Required: Access Token. The values come from your own LinkedIn account.

How are LinkedIn secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Does LinkedIn use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret, Expires At, Person URN): you approve access in LinkedIn, and the resulting tokens are stored encrypted like every other credential.

Nodes that use LinkedIn OAuth2

One credential works across every node below — create it once and reuse it.