Connectors

Connectors link PushFire to external delivery providers. Guides in this section are outbound—they let PushFire send email (and future channels) from your project. Audience data arrives separately through Integrations.

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

Authenticate inbound REST calls with a Public or Secret API key from Developers → API keys (Owner and Editor). Connectors store your provider API keys for outbound delivery.

Open Connectors in the sidebar (/connectors/home). Available to Owner and Editor.

• Email workflows, broadcast email, and email API messages require an active email connector
• Sender domains and API keys live in the connector configuration
• Without email infrastructure, email features are hidden or disabled in the console

• Resend — email API for Workflows, Broadcast, and API Messages
• SMTP — your own mail server from a single From email, TLS on port 465, for Workflows, Broadcast, and API Messages

Mailchimp, SendGrid, and Twilio appear in the console with a Coming Soon badge—they cannot be connected yet. See Coming Soon for the full list and how to reach the team.

The in-console item Connect your stack points here. Complete Resend or SMTP setup before creating email layouts or email broadcasts.