Zapier Integration with Firestore Query Setup Issues

Having trouble with basic Zapier and Firestore integration

I’m working on connecting Zapier to my Firestore database but running into problems. Every time I test the connection, I get an error message saying “We couldn’t find a record”.

I’ve been experimenting with different combinations of:

  • Collection paths
  • Document field names
  • Query parameter formats

But nothing seems to work correctly. The setup looks straightforward but I must be missing something fundamental about how Zapier structures queries to Firestore.

Has anyone successfully set up this type of integration? What are the common mistakes people make when configuring the path and field parameters?

Any guidance would be really helpful since I’m stuck on what should be a basic setup.

I encountered the same “We couldn’t find a record” error while setting up this integration a while ago. The issue often lies in the authentication permissions. Ensure that your service account has the correct Firestore roles assigned, particularly the “Cloud Datastore User” role. I initially had limited access with just basic Firebase permissions, which caused issues with Zapier’s API. Also, double-check your project ID in the connection settings; I had mistakenly used a test project, leading to the same frustrating symptoms. Unfortunately, the error message itself doesn’t clarify whether it’s an authentication issue or a problem with your query structure.

check your Firestore rules - mine only allowed authenticated users and that broke Zapier’s access. also double-check your collection name’s capitalization. Firestore is case sensitive and I wasted hours on a typo lol

Zapier’s document structure with Firestore is a pain. The trick is that Zapier wants the full document path, not just the collection name. Don’t test with empty collections - use actual docs that exist. Start with a basic document query to make sure your connection works, then add filters. Subcollections tripped me up - you need the complete path like “parentCollection/documentId/subcollection”, not just the subcollection name. Query a specific document ID first to figure out if it’s a path problem or something with your query parameters.