Docs

Integrations

Integrations

Inbound integrations overview

Inbound integrations connect your app or backend → Pushfire so real user activity can create and update subscribers, tags, segments, and workflows.

This is different from Connectors, which are outbound and connect Pushfire → external email/SMS providers (like Resend) for message delivery.

When to use what

  • Inbound (this section): Flutter SDK, FlutterFlow library, HTTP API, custom backend.
  • Outbound (Connectors): Configure email/SMS providers so Pushfire can send messages using your accounts.

For outbound delivery setup, use the Connectors guide in the docs.

Flutter & FlutterFlow

If you build with Flutter:

  • Use the official Flutter SDK to connect securely in real time.
  • Keep subscribers, segments, and tags in sync with in-app behavior.

If you build with FlutterFlow:

  • Use the FlutterFlow library to reduce boilerplate.
  • Manage audience and workflows with minimal custom code.

To proceed, follow the child guides under this section (e.g. Flutter + Pushfire, FlutterFlow, Dreamflow).

API & custom backends

For custom or server-side integrations:

  • Use the API Reference to send data and events from any stack into Pushfire.
  • Endpoints cover managing subscribers, tags, segments, and triggering workflows.

This lets any backend (Node, Laravel, Rails, Go, etc.) talk to Pushfire over HTTP.