How does OCNORA authenticate with Firebase Cloud Messaging?

With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.

What can I automate with Firebase Cloud Messaging?

3 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Firebase Cloud Messaging operation I need is not listed?

Where Firebase Cloud Messaging has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Firebase Cloud Messaging?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Firebase Cloud Messaging calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Firebase Cloud Messaging

Chat & messagingOAuth 2.0Connection test available

Send push notifications via FCM HTTP v1 to tokens, topics or conditions (Google OAuth2).

OCNORA ships 3 typed Firebase Cloud Messaging operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Firebase Cloud Messaging Firebase Cloud Messaging API docs ↗

Before you connect Firebase Cloud Messaging

Authentication: OAuth 2.0
Credential: {"client_id", "client_secret", "refresh_token"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Firebase Cloud Messaging

Operations, grouped by what they do to your data.

Create and send 3

A sample Firebase Cloud Messaging workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Firebase Cloud Messaging trigger is needed.
2
Send To Conditionfirebase_messaging.send_to_condition
Send an FCM notification/data message to a condition.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 3