Paste the URL
Open the Zapier or Make card on the form and paste the endpoint. Both are plain JSON POSTs to whatever URL you give them, so either one also delivers to your own service.
A webhook turns a form submission into an event in another system. The moment someone submits, Questionful POSTs the response as JSON to a URL you choose: into Zapier, into Make, or straight into a service you wrote yourself.
This is the piece that separates collecting data from doing something with it. A lead becomes a CRM record, a work request becomes a ticket, a registration becomes a calendar entry, and nobody retypes anything.
Open the Zapier or Make card on the form and paste the endpoint. Both are plain JSON POSTs to whatever URL you give them, so either one also delivers to your own service.
Optionally set a secret, and each delivery carries an X-Questionful-Signature header, sha256=<HMAC-SHA256 of the body>. Submit one test response and recompute it at your end before you trust anything.
The body carries the event, the form (uuid and title), the response (uuid and submitted time), every answer as question / name / value, and a flat data map of name to value.
Every attempt is logged as recent activity on the form, so a failing endpoint is visible rather than silent.
We would rather you find this out here than after signing up.
Yes. The Zapier and Make cards are plain JSON POSTs to any URL, so either one delivers to an endpoint of your own. There is no separate webhook card to look for.
Open the Zapier or Make integration card on the form and paste your URL. Both are plain JSON POSTs, so neither requires an account with those services. The card is just a webhook with a name on it.
They can be. Set a signing secret and every delivery carries X-Questionful-Signature: sha256=<HMAC-SHA256 of the body>, which your endpoint verifies before trusting the payload.
Delivery happens inline with the submission with a 15 second timeout and two attempts. There is no later retry, so a prolonged outage loses those deliveries. The attempt is logged on the form so you can see it happened.
The event name, the form uuid and title, the response uuid and submission time, an answers array of question / name / value objects, and a flat data object mapping field names to values. Uploaded files arrive as signed download links.
Not yet. There are no API tokens, no OAuth provider, and no JavaScript SDK. Webhooks and the standalone HTML export cover the developer-facing cases today.
Describe the form in a sentence and get a working question set back.
FeatureRoute each answer choice to its own section, so people only see what applies.
FeaturePoints per question, scoring on submit, and feedback that explains the answer.
Feature19 types, including specialist ones most builders skip.
FeaturePublic link, embed on your site, email to a list, or export standalone HTML.
FeatureScales, grids and summaries, questions built to aggregate.
Use caseQualify enquiries while they are being filled in, and hand every submission straight to the tool your sales process already runs on.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Unlimited forms and 100 responses a month. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.