Reference · Credentials
LinkedIn OAuth2 credentials
Used by 1 BusyBot node.
Type
linkedInOAuth2 6 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Access TokenaccessToken | password | Yes | — |
Refresh TokenrefreshToken | password | No | OAuth2 refresh token used to renew the access token after expiry (~60 days). |
Client IDclientId | string | No | LinkedIn App Client ID (required for automatic token refresh). |
Client SecretclientSecret | password | No | LinkedIn App Client Secret (required for automatic token refresh). |
Expires AtexpiresAt | number | No | Unix timestamp (ms) when the access token expires. Auto-managed. |
Person URNpersonUrn | string | No | Default LinkedIn person URN (e.g. urn:li:person:xxxxx) used as author when post param is empty. |
Setting up LinkedIn OAuth2
- 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.
- In BusyBot, open Credentials → Add credential and choose LinkedIn OAuth2.
- Paste each value into the matching field and save.
- 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 and are never shown again after saving.
- 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.
Nodes that use LinkedIn OAuth2
One credential works across every node below — create it once and reuse it.