Hey there, @FinTorro.com!

It seems as though there was an issue with the upload of that image as I’m not seeing any images attached here. Would you mind re-uploading the image so we can take a closer look at that query from step 2? 

Also, are you seeing any error messages when the query is run? If you are, could share a screenshot of the full error message (or copy and paste the text from it here)? Remember to remove/hide any private information (like names, emails, addresses etc.) from any screenshots before sharing. 

Thanks for your assistance on this, looking forward to hearing form you! 

 @SamB  Hi There, 

Thank you.

Just attaching here

I’m so sorry for the delay in a reply here, @FinTorro.com!

I did some testing in my own account and was able to get it working by updating the query to the following:

Here’s the code I used:

"where": {
        "fieldFilter": {
            "field": {
                "fieldPath": "documentId"
            },
            "op": "EQUAL",
            "value": {
                "stringValue": "Document ID goes here"
            }
        }
    }, 
"limit": 1

However, it was only able to work if a field called documentId field contained the path as well as the document’s ID number. As that’s what’s included in the selected ID field from the trigger step: 


If the documentId field in your database only includes the ID number then you’ll want to try using a Formatter (Text > Split Text) action to separate the ID number from the Path. Then in your Find Cloud Firestore Document action you’d use the ID that’s been extracted by the Formatter action, instead of selecting it from the trigger step.

Hope that helps. If you run into any further trouble on that please let me know, happy to help further!