Firebase Cloud Messaging
MessagingSend push notifications through Firebase Cloud Messaging. Agents deliver messages to individual device tokens, topics, or condition expressions, and manage topic subscriptions, authenticating with a Google service account.
What This Integration Enables
Push notifications are the one channel that interrupts a person mid-day, which is exactly why they should be wired to real events instead of campaign calendars. Firebase Cloud Messaging is Google's delivery rail for Android, Apple, and web push, and this connector puts it inside FlowRunner as a plain workflow action: agents send to a single device token, to a topic audience, or to a boolean condition combining topics, and they manage topic membership in bulk. Authentication is a Google service account, so agents send with scoped, short-lived tokens rather than a shared server key. The point is not sending more push. It is making push a consequence of orchestration: - Operational events become device notifications: an order confirmation, a task assignment, a document ready for review - Topic audiences stay accurate because agents update subscriptions the moment the underlying customer data changes - Condition expressions target intersections of topics, so one send reaches "tech industry AND watching this stock" without a segmentation project - Dry Run gives every send a rehearsal, so malformed payloads fail in validation instead of in a customer's notification tray - Platform overrides tune Android, APNs, and web push behavior per send without separate code paths Broadcast reach is also broadcast risk, and that is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer belongs: single-device operational sends run autonomously, audience-wide sends wait for a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order events reach the customer's pocket
A [Shopify](/integrations/shopify) order triggers the flow. The agent looks up the customer's app record, pulls their FCM registration token, and calls Send to Device Token with the order number in the notification body and the deep link in the data payload. When the 3PL posts tracking, the same flow fires again with the shipment update. If the token comes back unregistered, the agent flags the user record for cleanup instead of silently failing forever. No campaign tool involved, because these are not campaigns, they are receipts.
Segment topics that track the CRM, not the other way around
When [HubSpot](/integrations/hubspot) registers a new contact on the annual plan, the agent batches their device token into the plan-annual topic with Subscribe Tokens to Topic. When a customer churns or downgrades, Unsubscribe Tokens from Topic removes them in the same nightly batch, and the agent reads the per-token results array to catch tokens that failed with NOT_FOUND. When product marketing wants to announce a feature to annual-plan customers in the beta program, the agent uses Send to Condition with an expression combining both topics. The audience was maintained continuously by agents, so the send targets who the CRM says exists today, not who a CSV said existed last quarter.
The broadcast that had to pass a person first
An incident is resolved and the status workflow proposes an all-users notification via Send to Topic. The agent first runs the exact message with Dry Run enabled and posts the validated payload, the topic name, and the estimated audience description to [Slack](/integrations/slack). The on-call communications owner reads the wording, fixes one ambiguous phrase, and approves. Only then does the live send fire. The agent did the assembly, validation, and delivery at machine speed; the decision to interrupt every installed device stayed with a person who will stand behind the wording.
Human-in-Loop Highlight
Send to Topic has no undo. The moment it fires, every device subscribed to that topic gets the interruption, and a wrong message, wrong audience, or wrong moment is corrected only by a second notification apologizing for the first, which doubles the damage. So in FlowRunner, topic and condition sends above a single-device scope are gated: the agent composes the message, validates it with Dry Run, and presents the payload and target expression to a named owner for approval before live delivery. Send to Device Token for transactional events flows freely, because a shipping confirmation to one customer is recoverable. A broadcast to the entire install base is not, and the platform treats the two accordingly.
Agent Capabilities
5 actionsMessaging
3- Send to Device Token Sends a push notification to a single device using its FCM registration token. Combine a visible notification (title, body, image) with a custom data payload for your app to handle, and optionally tune platform-specific behavior for Android, Apple (APNs), and web push. Enable Dry Run to validate the message with FCM without actually delivering it.
- Send to Topic Sends a push notification to every device subscribed to a Firebase topic. Provide the topic name (with or without the "/topics/" prefix). Supports a visible notification, a custom data payload, and platform-specific overrides for Android, Apple (APNs), and web push. Enable Dry Run to validate without delivering.
- Send to Condition Sends a push notification to devices that match a boolean condition combining up to five topics, for example "'stock-GOOG' in topics && 'industry-tech' in topics". This targets the intersection or union of topic audiences in a single request. Supports a visible notification, a custom data payload, and platform-specific overrides. Enable Dry Run to validate without delivering.
Topic Management
2- Subscribe Tokens to Topic Subscribes up to 1000 device registration tokens to a Firebase topic in a single batch via the Instance ID API, so future "Send to Topic" and "Send to Condition" messages reach these devices. Returns a per-token results array; individual tokens may fail (e.g. invalid or unregistered) while others succeed.
- Unsubscribe Tokens from Topic Unsubscribes up to 1000 device registration tokens from a Firebase topic in a single batch via the Instance ID API, so they no longer receive messages sent to that topic. Returns a per-token results array; individual tokens may fail while others succeed.
Frequently Asked Questions
What can FlowRunner do with Firebase Cloud Messaging?
FlowRunner agents can run Send to Device Token, Send to Topic, and Send to Condition in Firebase Cloud Messaging, plus 2 more actions.
Does connecting Firebase Cloud Messaging to FlowRunner require OAuth?
Firebase Cloud Messaging uses a custom authentication method to connect to FlowRunner.
Can Firebase Cloud Messaging trigger a FlowRunner workflow automatically?
Firebase Cloud Messaging doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Firebase Cloud Messaging
$100 in credits. No card required. Connect in minutes.