Hey! First timer here. I’m trying to rebuild an app I had on Glide/Make over here on Firestore/N8N so forgive me but I’m new to both N8N and firestore.
I’m trying to create a document for each of my planners and for now I’m just trying to create a single field in each document. But, my basic question is how to structure the field data? I can’t find how to define the field name and value in the documentation. I’m trying to get “description” as the field name and my expression as its value.
The documentID is going nicely, but I’m struggling to understand how to then pass my columns/attributes in a way that maps to fields: data in Firestore.
For example, when I pass {{ $json.rows[‘8qfdO’] }} I end up with multiple fields whose names are all parts of by string separated by commas with “null” as each’s value.
Alternatively, when I try passing it in JSON such as “{
“description”: “{{ $json.rows[‘8qf0d’].toString().split(/[\n\r,]+/).join(’ ') }}”
}” I get it all in one field name, but again, the value is null.
Sorry, I’m 100% sure this is a basic dumby question from a newbie, but I’ve been at it for hours and can use the help. Thanks!
I ran the same operation in Make.com and it worked. The bundles had the structure: [
{
“path”: “/planners”,
“fields”: [
{
“value”: “text blah blah blah”,
“fieldName”: “description”,
“valueType”: “stringValue”
}
],
“documentId”: “Reading”,
“input_type”: “select”,
“project_id”: “mis”
}
]
Thanks Andrew, the http request works for me as well.
The only thing I had to doublecheck is the {projectname} which actually should be the {project-id} as those can be different and google needs the id of the project in the http request.
Thanks @leeh! It took me a bit to have the time to test this but yes, that setup for the module works! Though, I agree this should be looked at. For example, it’s not intuitive at all how to mix and match input modules if I want to take part from the previous module, but maybe something else from earlier. But you certainly got this working!