The Salesforce node currently doesn’t expose the standard `MiddleName` field when creating or updating Leads. `MiddleName` is a standard Salesforce API field (not a custom field), but it is missing from the list of available Lead fields in the n8n Salesforce node. Since it’s not a custom field, it also can’t be added via the Custom Fields option. It would be great if `MiddleName` could be added to the standard Lead fields so users can map it without having to use an HTTP Request node. Thanks!
Good catch. Since MiddleName is a standard (non-custom) Salesforce field, the Custom Fields option in the node won’t expose it either. Your best workaround right now is to keep using the Salesforce node for auth and the main Lead fields, then add an HTTP Request node right after it to PATCH the same Lead record with just the MiddleName field via the Salesforce REST API. That way you’re not rebuilding the whole Lead creation logic in HTTP Request, just patching the one missing field. Worth flagging this as a quick fix for the maintainers since it’s likely just a missing entry in the node’s field list.
I actually managed to make it work by just writing MiddleName in Custom Field
It shows an error next to it as you can see, but it works
As a workaround its ok, but it would be nice if it could be exposed properly as standard field
hi @flash99
Welcome to the n8n community!
As an alternative, if the business doesn’t actually use MiddleName, it could be disabled in Salesforce instead of introducing a custom field and a Flow. However, for organizations that do use it, exposing it as a standard field in the n8n node would still be a worthwhile improvement.