n8n - 💡(How to fix) Fix Salesforce Create Contact Node Account ID Field Not Loading [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#30700Fetched 2026-05-20 03:59:15
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

Hey guys,

This is an URGENT request as this bug has been killing us lately from further developing our AI GTM Infrastructure.

Please see below the ss:

<img width="360" height="615" alt="Image" src="https://github.com/user-attachments/assets/5d10423c-ab6f-4919-a7ca-b9b87c5339a8" />

I am trying to update a contact's Account ID field, but the field itself never loads.

This kills our whole flow.

Please fix ASAP.

Thank you!

To Reproduce

  1. Go to this n8n flow https://n8n.int.sundayapp.xyz/workflow/DB7562JeYFYqGc45
  2. Select the SF Create - New Contact node
  3. Search for the "Account Name or ID" field
  4. Notice how it still says "Loading options..."

This has been the case for days now.

Expected behavior

Expected behavior should allow me to select accounts options in the drop down or input my own variables as expressions from the previous nodes' runs.

Debug Info

Debug info

core

  • n8nVersion: 2.20.11
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.15.0
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: d22e9208-6f20-4804-abe8-19c9502fd11d

storage

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

pruning

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

client

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

cluster

  • instanceCount: 1
  • versions: 2.20.11
  • instances:
    • instanceKey: 486585a0-035c-4a23-a96d-e6080aba18ae, hostId: main-n8n-866dcf6fb-v54q2, instanceType: main, instanceRole: leader, version: 2.20.11
  • 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-05-19T09:32:55.327Z

Operating System

Alpine Linux v3.23

n8n Version

2.20.11

Node.js Version

24.15.0

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected behavior should allow me to select accounts options in the drop down or input my own variables as expressions from the previous nodes' runs.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING