Formstork

USE CASE

The backend for your bug report form

Formstork is the backend for your bug report form. Point any HTML or JavaScript form at it, and every report lands in a searchable dashboard, in your inbox with the reporter set as reply-to, and in the tools your team tracks bugs in. No server, no backend code.

How it works

When someone reports a bug, their form POSTs to Formstork with your access key. Formstork stores every report in a searchable, taggable dashboard, emails you a copy with the reporter's address set as the reply-to so you can ask for repro steps, and can forward it to Slack, Discord, Notion, Airtable, or a signed webhook your issue tracker can turn into a ticket. On paid plans, reporters attach a screenshot, screen recording, or log file, and a rules engine can route a critical bug straight to the right person. There is nothing to host and no database to run: your form stays plain HTML, and Formstork is the backend behind it.

Every report arrives with evidence

On a paid plan, reporters attach a screenshot, screen recording, or log file right in the form. The file is stored with the submission and downloadable from your dashboard, so a bug report shows you what broke instead of just saying it broke.

Straight into the tools you triage in

Each new bug can post to Slack or Discord, drop into a Notion or Airtable board, and hit a signed webhook your issue tracker or a small script turns into a ticket. Integrations are free on every plan and retried automatically if a service is down.

Route and tag by severity

The rules engine reads a severity or component field and sends a critical report straight to the person who owns it, so blockers do not sit behind low-priority noise. Tag, search, and filter every report in the dashboard, then export to CSV or JSON.

Set it up

  1. 1Add your bug report form as plain HTML with fields like email, summary, steps to reproduce, and severity, or build one in the Formstork form builder.
  2. 2Point the form's action at https://api.formstork.com/submit and add your access key as a hidden access_key field. To accept screenshots or log files, add enctype="multipart/form-data" and a file input (paid plans).
  3. 3Submit once to test. Each report lands in your inbox and your searchable dashboard, spam filtered, with the reporter's email set as the reply-to.
  4. 4Optional: add a rule to route critical bugs to the right person, connect Slack, Discord, Notion, or Airtable, or post to a signed webhook your issue tracker can turn into a ticket.

Frequently asked questions

How do I add a backend to my bug report form?

Point your form's action at https://api.formstork.com/submit and add your access key as a hidden field. That is the backend: Formstork receives the POST, stores each report in a searchable dashboard, and emails you with the reporter set as the reply-to. No server or backend code to write.

Can reporters attach screenshots or log files?

Yes, on a paid plan. Add a file input and set enctype="multipart/form-data", and reporters can attach a screenshot, screen recording, or log file. The file is stored with the submission and downloadable from your dashboard. File uploads are not available on the free plan.

Is it free, and can I send reports to Slack or my issue tracker?

Yes. The free plan covers 250 submissions a month with the full dashboard, email, spam filtering, and 90-day retention, no credit card. Integrations like Slack, Discord, Notion, Airtable, and signed webhooks are free on every plan, so you can forward each bug to your team's tools or your issue tracker. Paid plans add more volume, forever retention, and file uploads.

Try Formstork free

250 submissions a month with a full dashboard. No credit card required.

Get your access keyStart from a template