We recently received a communication about the upcoming change to Salesforce credentials in n8n, requiring a migration to the External Client App authentication method in Salesforce.
I reached out to support but haven’t received a response yet, so I’m checking here to see how others are approaching this migration.
In our case, Salesforce is used in many workflows, and the documentation mentions that all existing Salesforce nodes need to be updated to use the new credential. This could potentially require manually updating a large number of nodes.
So I had two questions for the community:
Has anyone already completed this migration? If so, how did you handle updating existing workflows?
Is there a way to update the credential globally (for example at the credential level), or another approach that would avoid having to edit every Salesforce node manually?
From what I understand of the Salesforce roadmap, the transition away from Connected Apps does not seem immediately urgent on the Salesforce side yet, so I’m also wondering how other teams are prioritizing this change.
Any feedback or best practices would be greatly appreciated.
Hi @Laurent_H Welcome!
If the systems are on a smaller scale i would say you can try using the manual method via n8n web UI, but like if you are working on a very large scale i recommend using the n8n API.
But in case if this is very urgent i would say you can use the API it is faster than manual!
@Laurent_H We cannot actually predict that would be there or not as officially n8n has not announced any deadline yet, for now all those login will work.
But you can always keep an eye here to watch out:
As there is no current information mentioned below that the credentials or specific login method would not work:
As long as salesforce is not gonna change how their API currently interacts with external resources trying to access it n8n would work fine, else even if something changes we always have HTTP node that is almost customizable to everything that any external API would require.