How to Add a Feedback Form to GitBook Docs
Embed a contact or feedback form directly in your GitBook documentation using an HTML block and Formboost. Collect bug reports, feature requests, and user feedback without leaving your docs.
How to Add a Feedback Form to GitBook Docs
GitBook is great for documentation, but feedback from readers usually means readers leaving to send an email or file a GitHub issue. With a Formboost-powered HTML block, you can embed a contact or feedback form directly in your GitBook space — readers submit without ever leaving the page.
Note: Custom HTML blocks require a GitBook Pro or Enterprise plan.
Use Cases
- End-of-page feedback — "Was this page helpful? Tell us what's missing."
- Bug report form — let users report docs errors inline
- Feature request form — structured submissions with category dropdowns
- Contact sales form — embedded in your pricing or enterprise page
Step 1: Create a Formboost Endpoint
Sign up at dashboard.formboost.app and create a new endpoint. You'll get a URL like:
https://formboost.app/f/YOUR_ENDPOINT_ID
Create a separate endpoint for each form type if you want separate dashboards and notifications.
Step 2: Add an HTML Block in GitBook
- In your GitBook page, type
/and search for HTML - Select the HTML block
- Paste the following:
1<form action="https://formboost.app/f/YOUR_ENDPOINT_ID" method="POST"
2 style="display:flex;flex-direction:column;gap:10px;max-width:480px;font-family:inherit;">
3
4 <input type="text" name="name" placeholder="Your name" required
5 style="padding:8px 12px;border:1px solid #d0d5dd;border-radius:6px;font-size:14px;" />
6
7 <input type="email" name="email" placeholder="Email address" required
8 style="padding:8px 12px;border:1px solid #d0d5dd;border-radius:6px;font-size:14px;" />
9
10 <textarea name="message" placeholder="Your message or feedback" rows="4"
11 style="padding:8px 12px;border:1px solid #d0d5dd;border-radius:6px;font-size:14px;resize:vertical;"></textarea>
12
13 <button type="submit"
14 style="padding:10px 20px;background:#346df1;color:#fff;border:none;border-radius:6px;font-size:14px;cursor:pointer;align-self:flex-start;">
15 Submit
16 </button>
17</form>Replace YOUR_ENDPOINT_ID with your actual endpoint ID.
Step 3: Add a Category Dropdown (Recommended)
For feedback forms, a category field helps you route submissions correctly:
1<select name="type"
2 style="padding:8px 12px;border:1px solid #d0d5dd;border-radius:6px;font-size:14px;">
3 <option value="feedback">General Feedback</option>
4 <option value="bug">Bug Report</option>
5 <option value="feature">Feature Request</option>
6</select>Add this inside the <form> before the message textarea.
Step 4: Pass Page Context
Know exactly which page a submission came from by passing it as a hidden field:
1<input type="hidden" name="page" value="Getting Started" />Update the value to match the page title where you're embedding the form. The page name will show up in your Formboost dashboard alongside the submission.
Step 5: Test It
Save the page and submit the form. The submission appears in your Formboost dashboard and triggers an email notification. If you've connected a webhook, it fires immediately too.
Routing Submissions by Type
Use Formboost's webhook integration to route different submission types to different places:
- Bug reports → create a GitHub issue via a GitHub webhook
- Feature requests → add to a Notion database or Linear project
- General feedback → post to a Slack channel