Open‑source maintainers love feedback, but exposing a raw mailto: address on a README, wiki, or website is a security nightmare. Spam bots crawl the web, harvest every email they find, and your inbox soon resembles a junk‑mail landfill.
Enter formcrab.com – a simple, code‑free solution that gives you a private, customizable link for bug reports, support requests, or any kind of user message. The link can be dropped anywhere (GitHub README, Twitter bio, static blog) and it works out of the box: the landing page, the form, and the backend are all provided and protected against spam.
Below you’ll find a step‑by‑step guide to get a private bug‑report link up and running for your project, plus tips on personalization, redirect handling, and webhook integration.
Why Use a Private Form Link Instead of a Plain Email Address?
| Problem | Traditional mailto: |
formcrab.com Private Link |
|---|---|---|
| Spam exposure | Bots harvest email directly from the page | Email stays hidden; only the tokenized link is public |
| Maintenance | Requires you to manage a mailbox, filters, auto‑responses | All messages are forwarded to your inbox with a clean subject line |
| User experience | Opens the user’s email client, which may be blocked or confusing | A friendly web form works on any device, no email client needed |
| Customization | Limited to subject line via URL encoding | Pre‑fill fields, set redirect URLs, add extra data via GET parameters |
| Anti‑spam protection | None | Built‑in CAPTCHA‑free protection (behavioural analysis) |
| Cost & hosting | Free, but you pay with time and spam | Free tier available, no server to host or maintain |
Getting Started in 3 Minutes
-
Create a Formcrab account – go to formcrab.com and sign up using your GitHub or email.
-
Generate a private token – once logged in, click New Form, give it a name (e.g., Open‑Source Bug Report), and click Create. You’ll receive a unique link that looks like
https://formcrab.com/f/AbC123xYz. -
Add the link to your project – paste the URL anywhere you want users to report bugs. For a GitHub README you might write:
**Report a bug** – [Open the bug‑report form](https://formcrab.com/f/AbC123xYz)
That’s it. When a user clicks the link they see a clean form, fill it out, and you receive the message straight to your inbox.
Customizing the Experience with GET Parameters
Formcrab lets you pre‑fill fields or control the post‑submission flow by appending query parameters to your private link. Replace {custom-link} with the token you received.
| Goal | Parameter | Example |
|---|---|---|
| Auto‑fill the user’s name | name |
<a href="https://formcrab.com/f/{custom-link}?name=Hugh" target="_blank">Email us</a> |
| Pre‑set the visitor’s email (when you already know it) | email |
<a href="https://formcrab.com/f/{custom-link}[email protected]" target="_blank">Contact Support</a> |
| Classify incoming messages with a subject line | subject |
<a href="https://formcrab.com/f/{custom-link}?subject=Urgent+Support+Request" target="_blank">Report an Issue</a> |
| Provide a template message to guide the user | message |
<a href="https://formcrab.com/f/{custom-link}?message=I+would+like+to+request+a+demo" target="_blank">Inquiry</a> |
| Redirect to a custom “Thank‑you” page after submit | next |
<a href="https://formcrab.com/f/{custom-link}?next=https://yoursite.com/success" target="_blank">Send and Return</a> |
You can combine multiple parameters, e.g.:
[Report a Critical Bug](https://formcrab.com/f/{custom-link}?subject=Critical+Bug&next=https://myproject.org/thanks)
All parameters are URL‑encoded, so spaces become + or %20.
Hooking Into Your Automation Pipeline (Webhooks)
If you prefer to process bug reports programmatically—e.g., create a GitHub issue automatically—Formcrab can POST the form data to any endpoint you provide. The JSON payload looks like this:
{
"name": "Hugh",
"email": "[email protected]",
"subject": "hello! there",
"message": "hello! there",
"submittedAt": "2026-03-12 10:20:08",
"extra": {
"key1": "value1",
"key2": "value2"
}
}
To enable a webhook:
- In your Formcrab dashboard, open the form settings.
- Turn on Webhook and paste the URL of your listener (e.g.,
https://api.myproject.org/bug-reporter). - Save.
Now every time a user submits the form, your endpoint receives a clean JSON object you can turn into a GitHub issue, send to a Slack channel, or store in a database.
Best Practices for Open‑Source Projects
| Practice | Why It Matters | How Formcrab Helps |
|---|---|---|
| Show a friendly UI | Lowers barrier for contributors | Formcrab provides a responsive, mobile‑friendly landing page |
| Avoid exposing personal email | Protects maintainers from spam & harassment | The private token hides your real address |
| Classify issues automatically | Saves triage time | Use the subject parameter to tag “Bug”, “Feature Request”, etc. |
| Redirect to project docs after submit | Keeps users engaged | next parameter can point to your CONTRIBUTING.md or a thank‑you page |
| Integrate with CI/CD | Auto‑create issues from form data | Webhook payload can trigger a GitHub Actions workflow |
Quick Checklist Before You Publish
- [ ] Generate the Formcrab token (
https://formcrab.com/f/…). - [ ] Test the link in an incognito window – verify the form appears and you receive the email.
- [ ] Add optional GET parameters for auto‑fill or custom redirects.
- [ ] (Optional) Set up a webhook that creates a GitHub issue.
- [ ] Paste the final link into your GitHub README, wiki, or project website.
Conclusion
Keeping your email address off the public web is a small change that pays huge dividends in security, spam reduction, and user experience. With formcrab.com, you get a ready‑to‑use, anti‑spam protected form that can be placed anywhere, customized on the fly, and integrated into your existing automation stack—without writing a single line of code.
Give it a try today, and watch the quality of bug reports improve while your inbox stays clean. Happy coding!