fb-group-extractor
What It Does
Section titled “What It Does”When people ask to join your Facebook group, you can take a screenshot of their request and upload it here. The tool reads the screenshot, pulls out the person’s name, where they live, where they work, and their answers to any questions your group asks. Then it sends all that info wherever you want it — usually straight to your customer list. It is the “screenshot mode” version of pulling data from Facebook, for when the live page scraping does not work.
When To Use
Section titled “When To Use”- When live scraping fails — Facebook’s DOM changes, new anti-scraping measures, or the group owner uses an odd layout. Screenshots bypass all of that.
- When you want a shareable team tool — the web app is designed to be multi-user (unlike most of the other FB extensions which are single-user).
- When you need an audit trail — the web app logs every upload and extraction to Supabase.
How To Install And Invoke
Section titled “How To Install And Invoke”Chrome extension:
- Load unpacked from
~/apps/fb-group-extractor/chrome-extension/atchrome://extensions. - Navigate to a Facebook group’s member-requests page. The extension overlay appears.
Web app:
cd ~/apps/fb-group-extractor && npm run dev- Frontend runs on
:3000, backend on:5001. - Default admin login:
ojhurst@gmail.com/admin123(change this).
Prerequisites
Section titled “Prerequisites”| Requirement | Where |
|---|---|
| OpenAI API key (optional, for GPT-4 Vision) | web app settings panel |
| Webhook URL (GHL or otherwise) | web app settings panel |
| JWT secret for auth | .env or server config |
| Supabase project (for logs and users) | migration files in repo |
| Manifest permissions | activeTab, storage, clipboardWrite, downloads; hosts: *.facebook.com, web.facebook.com |
Where It Lives
Section titled “Where It Lives”- Repo:
~/apps/fb-group-extractor/ - Chrome extension:
chrome-extension/manifest.json,popup.html,content.js,options.html - Backend:
server/index.js - Frontend:
client/src/ - Docs:
CHANGELOG.md,DEPLOYMENT.md
Known Gaps / Quirks
Section titled “Known Gaps / Quirks”- “Productizable” but not yet productized. README calls it multi-user and shareable, but the current config is hardcoded for a single group. Turning it into a real product requires generalizing the group-ID assumption.
- Has Vercel + Supabase config — the intent is clearly to deploy it as a SaaS at some point.
- Currently Build 3 on disk — still early.