Turn collaborators from new Firestore documents into Mailchimp subscribers
Firebase / Firestore + Mailchimp
To get started with Firebase on Zapier, first you will need to connect your Firebase project/account with your Zap
Next, you'll be asked to enter the Project's ID:
To find your Project's ID, please follow these steps:
Google will verify that you want to give permission for the integration to access the project:
If you have entered your details correctly, you will be successfully connected.
When using a Zap to trigger on new documents within a Firestore collection, it's important to build a Structured Query that returns the selected documents in the correct order, otherwise your Zap may never see the new documents.
orderBy property in your query needs to ensure that the new documents are at the "top" of the search results, so that the Zap can see those documents. In most cases, you'll want to use
DESCENDING, like this:
If your field has spaces in it, you will need to surround it with backticks. For example:
You can learn more about the correct syntax/structure here: https://cloud.google.com/firestore/docs/reference/rest/v1beta1/StructuredQuery#Order
When using a Zap to search for a specific document within a Firestore collection, it's important to build a Structured Query that contains the appropriate
where clause, like this:
In your Zap, the "compare to" value is probably something that you'll want to connect with a previous step within your Zap, using the "plus" button on the right-hand side of the input field within the Zap Editor.
You can learn more about the correct syntax/structure here: https://cloud.google.com/firestore/docs/reference/rest/v1beta1/StructuredQuery#Filter
Sometimes you will see an error that says "Invalid data; couldn't parse JSON object, array, or value. Perhaps you're using invalid characters in your key names."
This error occurs when the fields you are trying to send to Firebase contain invalid characters. Firebase prohibits key names from containing:
To get around the error, you will need to manually assign names to the keys. See the Customizing Fields to Store section for details.
New records need to appear at the end of your data for this to work. If you aren't using push IDs, your records need to be ordered lexicographically or by priority so that new records appear last.
A simple way to accomplish this is by calling
setWithPriority and using
Firebase.ServerValue.TIMESTAMP to order by timestamp.
Make sure you remove the beginning and ending
/ from the Path field.
Users sometimes encounter this error if anything that is being supplied in the value has a pipe ( | ) character in it. For example:
This has to due with the way our system encodes key/value pairs. The recommend solution is to not include invalid characters in the value that is included or use a Formatter step to remove the characters.
Get started with a Free account