Hi everyone,
I’m successfully connected to Salesforce using the n8n Salesforce node — authentication works, and I can retrieve data without issues. However, I’m having trouble setting up a trigger-based workflow.
When I try to activate a workflow that includes a Salesforce Trigger node (e.g., for new/updated records), I receive a “Bad Request” error. The workflow remains inactive.
So far, I’ve checked the following:
- The connected Salesforce account has API access.
- OAuth2 credentials are configured correctly and work for polling nodes.
- I’ve tried using different object types (e.g., Lead, Opportunity) in the trigger without success.
- I don’t see any meaningful logs that explain the “Bad Request.”
Has anyone encountered a similar issue or can provide guidance on what might be missing in the trigger setup?
We use the Enterprise Edition.
Thanks in advance!
Ben
1 Like
Hey,
What error comes with it, is it only Bad Request u see? anything in Logs or can you see further details in dev console?
That sound bit odd tbh
Hi,
the massage is not very helpfull.
Where in the DevConsole would you have a look?
THX!
Ben
Hey Ben,
So you can see in the console tab for errors, and network tab too to see payload or potential issues with payload request etc. Does it say bad request even when the trigger node has the green tick?
btw if u want u can share the workflow, I can try save and make active see if I get same error.
Best regards,
Samuel
Hi Samuel,
yes, I can see the green tick and if I run via “TestFlow”, everything runs fine! Only if I try to switch to “active”, i get the error.
Bildschirmfoto 2025-05-26 um 10.39.46|690x211
Thank you,
Ben
2 Likes
@Ben_jamin Hello again,
So, this is quite odd, have you tried to copy this into another workspace, or maybe try create a new workflow, and simple node, make active, then edit with the slaes force trigger maybe workaround it, hope you get resolved soon.
Samuel
