Best Invite Mechanisms for Launching Our Community

Jeremy G. · 2025-06-23 14:59:39.62135+00

Hey all! Wanting to "launch" our community by end of week and I'm struggling with the best invite mechanism. I'm wanting to send an announcement email for the initial round and have a button that takes them to sign up. Second will be an automation where users will get an email when they start to use our API or go to our internal product landing page. For 1 - What is the best landing page to send users to (knowing the invite link has a limit of 400)? For 2 - It looks like I can't automate the process without Enterprise API's (if I'm reading right)? What's the best mechanism with minimal friction to get everyone in? I see many using a form but, I can't conceptualize in my head how that would work without the .invite api access. Is there something I'm missing?

Best Invite Mechanisms for Launching Our Community | Tightknit Community

15 comments

· Sorted by Oldest

Zach H.
·
·
Remind me Jeremy G., is the community open or closed? As in, will you allow prospects or only customers in the space? That will change the approach. Our form, for instance, redirects to the join link at the very end! We update after every 200 users or so.
Loading attachments
Jeremy G.
·
·
Open community. Anyone is welcome
1
Zach H.
·
·
Then I would recommend also following the CTA Button settings to create a community.rhombus.com/join link if that was interesting
Jeremy G.
·
·
How are you tracking link being used 200 times? Just manually checking the admin page?
Zach H.
·
·
Today yes, but we used to have a feature that would notify you after 300 people joined. I wonder if it makes sense for us to bring that back. FYI Stephen C.
Jeremy G.
·
·
I think the initial blast is what I'm most worried about. We have about 4000 API users that will go out first. I can parse and send each 400 get a unique link so it won't go over ... Can't think of a better way for that portion.
Zach H.
·
·
I SEE. Yes, this is a challenging problem. We usually find that not all users will join immediately, but I understand the concern. Definitely recommend using a static link, but it might also make sense to stage the emails. The other option is to create a waitlist and then send out the invitations. (making notes for future products on our end that could help with this — waitlist, emails)
🙌1
Stephen C.
·
·
Jeremy G. For my own understanding, is there a way other than the admin API for 1 person to generate multiple invite links?
Zach H.
·
·
(there is not Jeremy G., just heads up!)
Jeremy G.
·
·
Not that I could find ... there's a TON of endpoints but Slack does a really good job of pay to play 🙂
😿1
1
Stephen C.
·
·
Ok gotcha, just confirming there wasn't a secret UI button I wasn't aware of!
Jeremy G.
·
·
I'm always looking for secret buttons! Normally we're pretty good at finding them haha
2
🎮1
Stephen C.
·
·
Jeremy G. This would make your invitations dashboard messy but throwing it out there - if you have the emails of all your users, you could copy+paste them into the invite modal input. This would invite each person separately. I bet there's a max number of emails that modal supports, but no idea what it is. In theory though this would avoid the 400 signup limit on a single link.
Zach H.
·
·
It’s 250. I wouldn’t recommend doing that because you have to revoke them in order to send out more.
Stephen C.
·
·
ohhhh right

Zach H.
·
·
Remind me Jeremy G., is the community open or closed? As in, will you allow prospects or only customers in the space? That will change the approach. Our form, for instance, redirects to the join link at the very end! We update after every 200 users or so.
Loading attachments
Jeremy G.
·
·
Open community. Anyone is welcome
1
Zach H.
·
·
Then I would recommend also following the CTA Button settings to create a community.rhombus.com/join link if that was interesting
Jeremy G.
·
·
How are you tracking link being used 200 times? Just manually checking the admin page?
Zach H.
·
·
Today yes, but we used to have a feature that would notify you after 300 people joined. I wonder if it makes sense for us to bring that back. FYI Stephen C.
Jeremy G.
·
·
I think the initial blast is what I'm most worried about. We have about 4000 API users that will go out first. I can parse and send each 400 get a unique link so it won't go over ... Can't think of a better way for that portion.
Zach H.
·
·
I SEE. Yes, this is a challenging problem. We usually find that not all users will join immediately, but I understand the concern. Definitely recommend using a static link, but it might also make sense to stage the emails. The other option is to create a waitlist and then send out the invitations. (making notes for future products on our end that could help with this — waitlist, emails)
🙌1
Stephen C.
·
·
Jeremy G. For my own understanding, is there a way other than the admin API for 1 person to generate multiple invite links?
Zach H.
·
·
(there is not Jeremy G., just heads up!)
Jeremy G.
·
·
Not that I could find ... there's a TON of endpoints but Slack does a really good job of pay to play 🙂
😿1
1
Stephen C.
·
·
Ok gotcha, just confirming there wasn't a secret UI button I wasn't aware of!
Jeremy G.
·
·
I'm always looking for secret buttons! Normally we're pretty good at finding them haha
2
🎮1
Stephen C.
·
·
Jeremy G. This would make your invitations dashboard messy but throwing it out there - if you have the emails of all your users, you could copy+paste them into the invite modal input. This would invite each person separately. I bet there's a max number of emails that modal supports, but no idea what it is. In theory though this would avoid the 400 signup limit on a single link.
Zach H.
·
·
It’s 250. I wouldn’t recommend doing that because you have to revoke them in order to send out more.
Stephen C.
·
·
ohhhh right