Integrations

Connect your app or backend to PushFire. Guides in this section are inbound integrations—they register subscribers, devices, and tags in PushFire. Outbound email is configured separately under Connectors.

• Inbound (this section) — Flutter SDK, FlutterFlow library, Node.js client, or REST API. Your code sends audience data into PushFire.
• Outbound (Connectors) — delivery providers such as Resend so PushFire can send email from your project.

Authenticate REST calls with the project Bearer token from Developers → API Token (Owner and Editor).

• Subscribers — externalId, profile fields, metadata
• Devices — FCM tokens, platform, push enabled flag
• Tags — labels for segments, broadcasts, and workflows

Segments are computed in PushFire from tag rules—they are not uploaded as a separate entity from your app.

1. Getting Started for Developers — prerequisites, API Token, integration flow, and console verification.
2. Flutter + PushFire — official SDK for native Flutter apps. Nested guides cover Flutterflow and Dreamflow.
3. Node.js + Pushfire — server-side client for backend integrations.

For HTTP from any other stack, use API Reference under Developers.

• Developers — API Token, API Messages, and API Reference
• Subscribers — verify test users after your first integration
• Connectors — required before email workflows, layouts, broadcasts, or API email messages

• Firebase credentials enable push delivery—they do not import subscribers on their own.
• The console has no CSV import or manual subscriber creation; data arrives via SDK or API.
• Do not follow legacy Firebase + FlutterFlow sync guides—use the current guides in this section.

• Audience sync — end-to-end inbound patterns and tag strategy
• Resend connector — outbound email setup
• Developers — API Token and API Messages in detail