I’m on n8n cloud on the latest version. Here’s my full workflow. I’m basically checking based on email and a string passed in if a contact and account exist in salesforce. Whether they do or don’t it pushes through the flow and ends up in the Merge Account Contact node.
The net result is that when I try my final salesforce node to assign the account to the contact, the contact data isn’t available with the structure I expected:
I’ve tried lots of things in there (like: {{ $('Merge Account Contact').item[0].json.accountId }}) and nothing seems to work.
I’m not sure what the issue is or if I’ve not set up my workflow to pull the data together correctly. Maybe there’s a better way to structure the flow and I have too many merges going on.
Maybe a broader question about n8n is why my workflow doesn’t complete the “Contact Id” before moving onto the nodes that try to use but the “Account Id” and “Contact Id” I assumed this was possible, but I also tried putting the merge in (see original post).
I think I sorted this out…the general problem was that if I search for an account or contact on Salesforce, it would return the ID as id. When I created an account or contact, it would return with the ID as Id. So depending on the combination of new/existing account and new/existing contact, the filters and merges I had wouldn’t work correctly.