Connect Firebase / Firestore and Intercom to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Firebase / Firestore with Intercom - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Child Object in a Firebase Realtime Database" from Firebase / Firestore.
Add your action
An action happens after the trigger—such as "Add Note" in Intercom.
You’re connected!
Zapier seamlessly connects Firebase / Firestore and Intercom, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- PathRequired
- Order
- Location of newest objects
Try ItTriggerPolling- PathRequired
- Convert Numerics
- NewId
- Data
ActionWrite- Api_docs_info
- Stop on errorRequired
- HTTP MethodRequired
- URLRequired
- Query string parameters
- Additional request headers
- Body
ActionWrite- CollectionRequired
- QueryRequired
ActionSearch
- CollectionRequired
Try ItTriggerPolling- CollectionRequired
- Convert Numerics
- Document ID
- Data
ActionWrite- PathRequired
- Child keyRequired
- Search valueRequired
- Wrap search value in quotes
- Location of best match
ActionSearch- Lead Added Email
Triggers when a Lead enters an email address.
Try ItTriggerInstant
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Firebase / Firestore on the Zapier blog
Learn how to automate Intercom on the Zapier blog
Frequently Asked Questions about Firebase / Firestore + Intercom integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Firebase / Firestore and Intercom
How do we trigger an action in Intercom when a Firestore document is updated?
By using Firebase's Firestore triggers, you can set up a function to listen for specific changes in your Firestore database. Once a specified document is updated, the trigger can initiate an action in Intercom such as sending a message or updating user attributes.
Can we automatically create new Intercom users when new documents are added in Firestore?
Yes, our integration allows for the automatic creation of new Intercom users when a new document is added to a specified Firestore collection. A Cloud Function can trigger on document creation to handle this.
Is it possible to update Intercom user attributes based on Firestore data?
Absolutely. When changes occur in specific fields within your Firestore database, you can use these updates as triggers to modify the corresponding user attributes in Intercom.
What do we need to set up before integrating Firebase with Intercom?
Before integrating Firebase with Intercom, ensure you have both Firebase and Intercom accounts set up. Additionally, proper permissions and API keys from both platforms are necessary for seamless integration.
How can we use Firestore data to send targeted messages via Intercom?
You can create Cloud Functions that react to certain data conditions or changes within your Firestore. These functions can trigger personalized messages sent through Intercom based on the criteria met by your stored data.
Are there limitations on the types of data we can sync between Firestore and Intercom?
While most user-related data types are supported, some complex or large datasets might require optimization before syncing due to size and complexity limitations inherent between systems.
How do error-handling and retries work during integration tasks between Firebase and Intercom?
When setting up triggers between Firebase and Intercom, it's important to include robust error-handling mechanisms within your Cloud Functions. This includes setting retry policies for transient errors during data synchronization tasks.