Integration · Cloud and hosting
AI agents for Firebase Cloud Messaging
Send push notifications and data messages to Android, iOS and web apps through Firebase Cloud Messaging (FCM HTTP v1).
- Actions
- 7
- Read
- 1
- Write
- 6
Actions
What your agents can do in Firebase Cloud Messaging
Send push notifications and data messages to Android, iOS and web apps through Firebase Cloud Messaging (FCM HTTP v1): to one device, to everyone subscribed to a topic, or to a topic condition, and subscribe or unsubscribe devices from topics. Signs in with a Google service account key.
Read 1
Look things up. Nothing changes.
List a device's topics
Lists the topics one app install is subscribed to.
Write 6
Create, change or send.
Send to a device
Sends a push notification (a title, body and optional image) and/or a data payload to one app install, by its FCM registration token.
Send to a topic
Sends a push notification and/or data payload to every app install subscribed to a topic, like news or orders-eu.
Send to a topic condition
Sends to the devices that match a condition over up to five topics, like 'sports' in topics && ('us' in topics || 'ca' in topics).
Send a custom message
Sends a full FCM v1 message object, for what the simple sends do not cover: per-platform settings in android, apns (iOS headers and payload, badge, sound) and webpush, fcm_options, and collapse keys.
Subscribe a device to a topic
Subscribes one app install (its registration token or Firebase installation ID) to a topic, so it gets the topic's messages.
Unsubscribe a device from a topicDeletes data
Removes one app install's subscription to a topic, so it stops getting the topic's messages.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Firebase Cloud Messaging gives you for its API.
What you enter
- Service account key (JSON)
Settings
- Firebase project ID
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Firebase Cloud Messaging data
Ask a question in plain words. The agent can list a device's topics in Firebase Cloud Messaging, then answers with what it found.
- 02
Let an agent update Firebase Cloud Messaging
Have the agent send to a device or send to a topic in Firebase Cloud Messaging as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Firebase Cloud Messaging and Slack: it can list a device's topics in Firebase Cloud Messaging and post a summary to a Slack channel in the same run.
Works well with
More Cloud and hosting tools
- Amazon Web Services7 actionsEvery AWS service from one connection: EC2, S3, Lambda, RDS, DynamoDB, IAM, ECS, EKS, CloudWatch, Bedrock and over four hundred more.
- Microsoft Azure7 actionsEvery Azure service from one connection: Virtual Machines, Storage, App Service, Functions, AKS, SQL, Cosmos DB, Key Vault, Networking, Monitor, OpenAI and every other resource provider of Azure Resource Manager.
- Google Cloud7 actionsEvery Google Cloud API from one connection: Compute Engine, Cloud Storage, BigQuery, Cloud Run, GKE, Cloud SQL, Pub/Sub, IAM, Vertex AI and two hundred more.
- Amazon S38 actionsList buckets and files, read and download files, upload any file, save JSON files and delete files in Amazon S3 (Simple Storage Service), signed with an AWS access key.
- Netlify5 actionsList sites and their deploys, start a build, check a deploy's status, and roll a site back to an earlier deploy, on the Netlify teams a personal access token can reach.
- Heroku16 actionsSee Heroku apps, dynos, releases and builds, restart dynos, scale process types, roll back a release and switch maintenance mode, with a Heroku API token.
FAQ
Firebase Cloud Messaging and MyDeepAgents
Can MyDeepAgents connect to Firebase Cloud Messaging?
Yes. The Firebase Cloud Messaging connector has 7 actions: 1 reads and 6 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Firebase Cloud Messaging?
Enter the sign-in details Firebase Cloud Messaging gives you for its API. You'll need: Service account key (JSON). The connection also asks for: Firebase project ID. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Firebase Cloud Messaging without asking?
Only if you let it. Each of the 6 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Firebase Cloud Messaging in workflows as well as agents?
Yes. Every Firebase Cloud Messaging action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Firebase Cloud Messaging to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.