Web Forms

Create support forms for your website or documentation site. When a visitor submits a form, it creates a GitHub Issue or Discussion with all the form data — just like an email.

Embeddable widget

Creating a form

Use the /create-form command in any issue or discussion comment:

/create-form Contact Support

Scitor responds with an embed code containing a unique form ID.

Embedding the form

Add the provided iframe code to your website:

<iframe
  src="https://www.scitor.io/forms/abc123"
  width="100%"
  height="600"
  frameborder="0"
  title="Contact Support"
></iframe>

Docs contact form

You can embed a contact form directly in your knowledge base site. Unlike the embeddable widget, the docs contact form is configured in scitor.yaml and automatically managed — no /create-form command needed.

Setup

Add a contact section to your docs configuration:

docs:
  path: docs
  title: "My Support Docs"
  contact:
    placement: [footer, floating]

That’s it. On the next build, Scitor creates a form automatically and embeds it at the specified locations.

Placement options

Choose where the form appears by adding one or more placements:

You can combine multiple placements. For example, a footer for visibility and floating for quick access from anywhere:

docs:
  contact:
    placement: [footer, floating]

Customization

Customize the form title and description:

docs:
  contact:
    placement: [footer]
    title: "Need help?"
    description: "Drop us a line and we'll get back to you within 24 hours."

Spam prevention

The docs contact form includes three layers of spam prevention, all handled automatically:

1. Honeypot field — A hidden field that bots fill in but humans don’t see. Submissions with this field filled are silently accepted (the bot thinks it succeeded) but discarded.
2. Cloudflare Turnstile — A privacy-preserving CAPTCHA alternative. Scitor provides the Turnstile widget by default. If you prefer to use your own Turnstile site key, set turnstile_site_key in the config.
3. Rate limiting — Server-side limits of 10 submissions per IP address per hour and 5 per email address per hour. Exceeding these limits returns a rate limit error.

What gets captured

Each form submission includes:

Processing

Form submissions go through the same pipeline as emails:

1. Issue/Discussion created with form data in the body
2. AI analysis applied (Pro plan) — sentiment, category, summary
3. Labels applied automatically
4. Metrics tracked — counts toward inbound_forms

You can reply to form submissions using the same /send command as emails.

Custom metadata

Pass additional metadata to the form via URL parameters:

<iframe
  src="https://www.scitor.io/forms/abc123?metadata.page=/pricing&metadata.plan=pro"
  ...
></iframe>

Metadata fields appear in the issue body, helping you understand the context of each submission.