Slackin is dead. Here's how to run a Slack invite page in 2026

If you still have a slack.yourcommunity.com bookmark that returns an error — or a README badge that froze on “0 users online” — you are not alone. Slackin, the open-source invite landing page that defined public Slack communities for years, no longer works as a drop-in tool for most teams.

What you’ll learn

• What Slackin was, and why organizers depended on it
• Why the original project stopped being a viable option
• How to run a Slack invite flow for free in 2026 (including the boring, reliable methods)
• What hosted alternatives actually buy you
• When a purpose-built invite page is worth considering

What Slackin was

Slackin was a small Node server — created by Guillermo Rauch — that gave public Slack communities two things people desperately wanted:

1. A landing page where a visitor typed an email and received a workspace invite
2. Live badges (iframe / SVG) showing how many people were currently online

For open-source projects, local meetups, and “come hang out in our Slack” developer communities, that combination was magic. You pointed a subdomain at Slackin, pasted a badge in your README, and growth felt automatic.

People used it because Slack did not ship an equally simple public join experience. Workspace admins could invite colleagues one by one, but there was no polished, shareable “apply with email → get invited” page aimed at strangers on the internet. Slackin filled that gap with a weekend-sized deploy.

Why it stopped being maintained

Slackin’s design assumed Slack APIs and authentication styles that Slack later tightened. Two changes mattered most for operators:

• Legacy tokens went away. Early Slackin setups relied on user/legacy tokens that Slack stopped supporting for new use. Without a supported token story, fresh installs could not authenticate the way the README described.
• Invite APIs got gated. The Admin API method many “email me an invite” tools want — admin.users.invite — is documented as an Enterprise capability with admin scopes. That is a different world from the free public community Slackin optimized for.

Community forks tried to keep pace. The original issue tracker still shows years of “it broke again” reports after Slack API changes. A fork on GitHub is not the same as a safe production dependency.

Meanwhile Slack shipped shareable invite links from the workspace UI. For many teams, that native link replaced the core reason to run Slackin: you no longer needed a custom server just to hand someone a join URL.

The manual / free method (do this first)

You do not need a SaaS product to invite people to Slack in 2026. Start here. Be honest with yourself about the tradeoffs.

Option A — Slack’s own invite link on a static page

This is the default replacement path most former Slackin operators ended up on.

1. In Slack (desktop or web), open your workspace settings and find the controls for inviting people / invite links. Exact labels move around as Slack redesigns settings, so use Slack’s current help article for “invite people to your workspace” if you cannot find the screen.
2. Create an invite link. Choose the channel defaults Slack offers (for example, which channels newcomers land in) carefully — public communities often over-invite people into noisy spaces.
3. Note the expiration and usage limits Slack shows for your plan. Historically, free workspaces have lived with shorter-lived links than paid ones; do not assume “never expires” unless the UI explicitly says so for your workspace.
4. Put that URL on any page you control:
   • a single HTML file on Cloudflare Pages / Netlify / GitHub Pages
   • a section on your existing marketing site
   • a Notion page (works, though it looks like Notion)
5. If the link can expire, set a calendar reminder before it dies. Prefer one canonical landing URL you control (and update behind the scenes) over pasting the raw Slack URL across old tweets and slide decks.

What you get: zero hosting bill for the invite logic, Slack-native join UX, no custom code.

What you give up: live online counts, email capture before join, approval workflows, and spam controls beyond what Slack provides.

Option B — Open signup / email-domain rules (when they fit)

Some communities are not “anyone on the internet.” They are “anyone with an @company.com email” or “students at this school.”

Slack has long supported org-oriented signup patterns (for example, allowing people with certain email domains to join). If that matches your membership rule, configure it in Slack and link people to your workspace’s normal signup entry points instead of inventing a custom inviter.

Check Slack’s current documentation for approved email domains and related signup settings — availability depends on plan and workspace type. This path is excellent for internal or alumni communities and a poor fit for a fully public hobby Slack.

Option C — Self-host Slackin or a fork (high risk, usually not worth it)

You can clone the old project or a fork and try to make invites work again. Budget for API drift, token hygiene, dependency rot, TLS/host patching, and owning the emails you collect. If you still want to try: read recent commits and open issues (not star counts), confirm the Slack methods it calls are available on your plan (admin.users.invite is Enterprise-scoped in Slack’s docs), and run it in a throwaway workspace first.

For most organizers, this fails a simple test: the maintenance cost exceeds the benefit of a custom email form.

Option D — Manual invites from Slack (small communities)

If you are under a few dozen members and grow slowly, the free method is: a Typeform / Google Form → spreadsheet → you click Invite in Slack. It does not scale, and it feels undignified after Slackin — but it is secure, free, and honest. Several excellent communities still run this way on purpose.

Tool-assisted options (fair comparison)

When the manual path starts hurting — expired links, no screening, no single branded URL — people reach for tools. Categories, not a shopping list:

1. Generic landing-page builders + a Slack link

Carrd, Framer, Webflow, a plain HTML page. You write the story of the community, add a big “Join the Slack” button, and point it at Slack’s invite URL.

• Pros: Cheap or free, full design control, easy for marketers
• Cons: You still babysit link expiration; no approval queue; the form (if any) is disconnected from Slack unless you build glue

This is the right move when you mainly need positioning and trust, not automation.

2. Form tools + Zapier/Make + Slack

Typeform / Tally / Google Forms collecting applicants, with an automation that notifies moderators (or, on Enterprise, attempts an invite via API).

• Pros: Great questions, logic jumps, spreadsheets you already understand
• Cons: Multi-step glue; Zapier bills add up; auto-invite is still plan-limited on Slack’s side; someone must handle the “approved → actually invited” gap on most plans

Use this when applications are the product (fellowships, paid cohorts, gated professional networks).

3. Community platforms that are not Slack

If your real problem is “Slack is the wrong home,” Discord + a landing page — or a hosted community like Circle or Skool — may be the broader alternative. That is a migration decision, not an invite-page decision. Only switch homes if members will actually follow you.

4. Purpose-built invite-page products

A small category of products — Inviter included — treat the public invite page as the product: branded URL, applications, approval, anti-abuse checks, sometimes events. You keep Slack (or Discord/Telegram/WhatsApp) as the chat home. Evaluate Slack support on your plan, what happens after approval, spam controls, price past the free tier, and data portability.

How Inviter does it

Inviter’s Slack invite pages are a hosted front door for a workspace you already run. You publish a public page, collect applications, approve (or auto-approve) people, and connect Slack alongside Discord, Telegram, or WhatsApp if you use more than one home.

What is factual and worth knowing if you evaluate it:

• Free to start
• Applications with approval, email verification, country allow/deny rules, and captcha
• Events with Stripe ticketing (platform fee 10% on Free and 5% on Pro, plus Stripe’s fees)
• Pro at $19.99/month or $191.90/year
• Used by 1,200+ communities

If you are comparing costs, see pricing. If you want examples of public Slack communities already on the pattern, browse /communities/slack.

Inviter is optional. The free methods above are enough for many groups. Use a hosted page when the invite URL itself has become an ops problem — or when you need screening before strangers land in Slack.

Pick a path

Situation	Practical choice
Tiny community, low spam	Slack invite link on a simple page + calendar reminder
Email-domain membership	Slack’s domain / signup settings
You love running Node	A carefully vetted fork — knowing you own the breakage
You need applications + a stable public URL	Form stack or a purpose-built invite page

Slackin earned its legend because it made public Slack feel open-source friendly. The replacement is less romantic: Slack’s own links, a page you control, and clear ownership of who gets in. That combination is enough for most communities in 2026 — and when it is not, you now know exactly which layer is missing.