Guides
Guides
Multi Condition Node
The Multi condition node splits a PushFire workflow into ordered If branches plus Else. Tag conditions inside a branch are AND; the first matching branch wins. Unmatched subscribers take Else.
Stop Node
The Stop node ends a subscriber journey at that point. Later nodes on the same path do not run. On a Condition or Multi condition lane, only that lane exits.
Public and Secret keys
Platform Public (pf_pk_) and Secret (pf_sk_) keys: allowed actions, rotation, and how to store each credential.
Legacy credentials and migration
Keep the deprecated Legacy key while you adopt Public and Secret, then revoke Legacy when production is verified.
Restricted keys
Create named Restricted keys (pf_rk_) with a custom scope set for least-privilege integrations.
API keys
Public, Secret, Restricted, and Legacy credentials: how PushFire authenticates API calls and where to manage keys in the console.
Coming Soon
Mailchimp, SendGrid, and Twilio connectors shown as Coming Soon in the console—and how to contact the team.
Getting Started for Developers
Prerequisites, API Token, available stacks, and verification flow for integrating PushFire with your app or backend.
Console
Map of the PushFire Console sidebar—sections, roles, and links to detailed guides for each workspace area.
Project settings
Settings hub: General, Payment & Billing, and Members.
Developers
API keys, API Messages, and API Reference for authenticating and sending programmatic push and email.
Messaging
Workflows vs Broadcast—how Messaging is organized in the console.
Broadcast
One-off push and email campaigns without building a workflow.
API Token (deprecated)
Deprecated. PushFire now uses API keys (Public, Secret, Restricted, Legacy). Use the API keys guides instead.
Payment & Billing
Manage subscription plans, payment methods, and billing history (Owner only).
Support
Submit bug reports and feature requests from Support—what to include, what the console attaches, and when to use docs instead.
Members & Roles
Invite members, assign Owner/Editor/Viewer roles, and manage pending invitations.
General
Edit project name, description, and Firebase Service Account credentials.
API Messages
Programmatic push and transactional email from your backend.
Projects & workspaces
List projects, create a workspace, and switch between projects in the console.
Broadcast Push Notifications
Create, send, and track broadcast push notifications.
Email Layouts
Create and publish reusable HTML email layouts for workflows and broadcasts.
Broadcast Email Notifications
Create and send broadcast HTML emails with connector, sender, and layout.
Project dashboard
Project dashboard: metrics, Audience Intelligence, Campaign Performance, and Source Strategy.
Resend connector
Configure Resend API key, domain verification, and senders.
Connectors
Outbound connectors—Resend for email today and more providers coming soon.
Layout Configuration
Email layout configuration allows you to define a reusable visual structure for all emails sent from PushFire. A layout includes a header and a footer that wrap the content defined in each Email Notification Node. This functionality ensures visual consistency, email client compatibility, and compliance with best practices for email design and security.
Email Notification Node
The Email Notification Node enables sending personalized email messages as part of automated workflows in PushFire. It simplifies domain verification, sender management, and layout configuration to ensure visual consistency and strong deliverability. Each email supports full HTML content and dynamic parameters per subscriber, making it ideal for detailed, persistent, and engagement-focused communications.
Push Notification
The Push Notification Node in PushFire allows sending push notifications within automated workflows using Firebase Cloud Messaging. It supports delivery to Android, iOS, and Web, with customizable titles and bodies using dynamic subscriber parameters. It is a communication node designed for immediate alerts, reminders, and re-engagement, natively integrated into workflows with timing control and conditional logic.
Condition Node
The Condition Node in PushFire evaluates subscriber conditions and splits workflow execution into True and False branches. It primarily relies on tags and logical operators to personalize flows based on subscriber state, behavior, or attributes. It is a core node for dynamic segmentation and flow control, ensuring valid branches and automatic convergence within the workflow graph.