TypeError: additionalFields.group.map is not a function
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Contacts/GoogleContacts.node.js:161:72)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/Workflow.js:598:51)
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:557:68
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Information on your n8n setup
n8n version: 0.190.0
Database you’re using (default: SQLite): SQLite
Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
Hi @MortgageRockstar, can you try using an expression such as {{ ["contactGroups/myContacts"] }} like shown below? It seems the node expects an array (and Google Contacts requires the contactGroups/ prefix).
n8n will complain about an unsupported value but the contact was still created as expected for me:
I formatted an expression per your example and it worked. It does not appear to support the Group name as a string though, only the Group ID as a number.
It didn’t work for me when I used the Group name rather than the Group ID so that’s why I asked. Sorry I didn’t point that out in my previous response.
The node works if a Group ID is entered, but it does not work if you use a Group name as an expression. It does work if you select a Group name from the list as a fixed value (not as an expression).
Also I removed the value entirely as a test as you suggested and it worked fine too.
It appears that the node only does not work when using a Group name as an expression for some reason. Maybe that is not supported?
Can you run the below on it’s own and let me know if that works? Looking at the earlier example it is using an expression so that should be fine, I think there is maybe something earlier in the workflow that is causing the issue which we can’t see.
@Jon, I ran the Google Contacts node on its own with your example and my Group name Leads and it failed (see below).
This example executed successfully with the Group ID number for this same Group name (Leads). It just doesn’t like the Group name in the expression for some reason.
Well that is odd, Let me set up Google Contacts and I will take a look. If it is failing I am not sure how it was previously working unless myContacts is a special group.