Bug Description

While working on larger n8n flows to stream data to Salesforce, I found that within the same n8n flow all Salesforce actions are using an individual just created session.

Observation:

• The login history shows multiple logins within a short period of time for each n8n Salesforce action. It matches the exact number of Salesforce Actions in your n8n flow. This let's us assume that a new login is done with each n8n Salesforce action.
• When the limit is exceeded n8n receives an error code 400 and { "error": "invalid_grant", "error_description": "login rate exceeded" }

Why is this an issue?

• There is a login rate limit of 3.600 / hour. Especially if you are running batches with complex Salesforce query-actions, you are hitting the rate limit REALLY FAST.
• Once the limit is exceeded your user is banned from logging in until the sum of logins witihin the last 60 minutes is below 3.600 (see https://help.salesforce.com/s/articleView?id=000381578&type=1).
• In short: n8n is basically blocked from operating within that timeframe. ALL n8n-Flows using the credential are running into an error.

To Reproduce

Reproduce the issue: Your credential for Salesforce should be prepared. Our example is using OAuth2 JWT. Step 1: Create a n8n-Flow with manual trigger Step 2: Create 3-4 simple Salesforce actions in line for example query an Account with a specific Id. Step 3: Manually trigger the flow. Step 4: Open the User that is running the credentials / session in Salesforce and scroll down to "Login History".

Expected behavior

Expected Behavior

• n8n establishes a Salesforce session when the first Salesforce action is triggering.
• All following actions re-use the Salesforce session, drastically reducing the logins.

Debug Info

Debug info

core

• n8nVersion: 2.23.4
• platform: docker (self-hosted)
• nodeJsVersion: 24.15.0
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: b4dc8325-1628-45ee-8eb3-93e2bb001223

storage

• success: all
• error: all
• progress: false
• manual: false
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 192 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/149.0.0.0 safari/537.36
• isTouchDevice: false

cluster

• instanceCount: 1
• versions: 2.23.4
• instances:
  • instanceKey: 6863cd43-4835-4248-84b2-afb4913ae7bf, hostId: main-da34a0365218, instanceType: main, instanceRole: leader, version: 2.23.4
• checks:
  • check: hostid-clash, status: succeeded, warnings: -
  • check: lifecycle, status: succeeded, warnings: -
  • check: split-brain, status: succeeded, warnings: -
  • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-06-09T06:29:25.954Z

Operating System

Linux

n8n Version

2.23.4

Node.js Version

24.15.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted