Integrations

Submissions go where you work.

A form backend shouldn't stop at your inbox. Every FormWire integration is a per-form toggle: submissions are stored first, then fanned out to the destinations you switch on: no glue code, no middleware.

How integrations work

Store first, then fan out.

  1. Step 01

    Submission lands

    Every POST is stored durably before anything else happens, so an integration hiccup can never lose the submission itself.

  2. Step 02

    You toggle destinations

    Each form has its own Integrations tab. Switch on a destination, paste its endpoint or connect it, and choose which submissions it receives.

  3. Step 03

    Delivery you can see

    Each destination gets its own delivery attempt with retries, and the dashboard shows per-submission status: delivered, retrying, or failed.

Destinations

Live today, and what's next.

Email and signed webhooks ship today. Between them they reach anything with an inbox or an endpoint. Native one-click destinations are rolling out next.

Email (live)

Delivered to your verified inboxes, with retries and per-submission status.

Webhooks (live)

A signed HTTP POST (x-form-signature) to your endpoint for custom pipelines.

Slack (coming soon)

New-submission messages into the channel your team watches.

Discord (coming soon)

Route submissions into your community server.

Google Sheets (roadmap)

Append each submission as a new row.

Zapier (roadmap)

Fan out to thousands of apps for CRMs and anything exotic.

Integration questions

Want a destination we haven't listed?

Tell us
Ready in a minute

Connect your first integration.

Free tier forever. No credit card required.