Send clean answers to Generic Webhook.
Turn every submission into the handoff your team expects - an alert, a new record, a row, a task, or an automation - the moment someone hits submit.
- New website lead -> Generic Webhook -> team follows up
- Application or file upload -> Generic Webhook -> owner notified
- Feedback submission -> Generic Webhook -> sorted and handed off
Use a generic webhook when you need Formspring’s richest JSON envelope, optional field filters, payload field picks, or renames before data leaves Formspring, or when you want to verify each request with an HMAC signature. This path is ideal for internal services, bespoke backends, or middleware you host yourself.
What you get with Generic Webhook.
- Send a structured JSON payload to any system you control
- Optional filters and field maps from the Formspring dashboard
- Cryptographic signing so your server can trust the payload
- Same delivery logs, retries, and **Replay** as other integrations
Up and running in five steps.
- In Formspring, open the form → Integrations → add Generic Webhook (or equivalent) → paste your HTTPS URL.
- Optionally configure payload controls (filter by a field, include only certain keys, rename keys).
- Save, copy the signing secret from the integration detail if your receiver needs it.
- Send a test submission; your endpoint should log headers and body.
- Verify
X-Formspring-Signature(t=…,v1=…) against the raw JSON body, then confirm Deliveries shows 2xx.
Why teams use generic webhooks
Sometimes you need a signed JSON contract, filtered fields, or a destination that is not listed as a built-in provider. This integration is the escape hatch-same reliability features, your code stays in control.
Reliability and retries
Formspring retries failed deliveries with exponential backoff (up to eight attempts over several hours). Each attempt appears in Deliveries with the HTTP status and response body. Use Replay after you fix the issue on the receiving side.
Security: HMAC signing
Formspring adds X-Formspring-Signature: t=<unix>,v1=<sha256> computed over the exact raw JSON body (Stripe-style). Only generic webhooks receive this header.
Payload controls
From the webhook edit screen you can optionally limit which submissions fire (field filter), include only selected payload keys, or rename keys before signing-features that apply to generic webhooks, not to built-in provider cards.