Sync messages, images, replies, edits, deletes, and more between Discord and GroupMe in minutes.
- β Messages
- β Images
- β Replies
- β Edit Notifications
- β Delete Notifications
- β Messages
- β Images
- β Replies
- β Usernames
- β User Avatars
- π Multiple Bridges
- β‘ Automatic Discord Webhooks
- βοΈ Cloud Hosted
- πΎ SQLite Database
- π Quick Setup
- π Open Source
Deploy your own GroupCord backend for free using Northflank while using the official GroupCord Discord bot.
Average setup time: 10β15 minutes
Click the button at the top of this page to invite the official GroupCord bot to your Discord server.
π‘ Tip: Right-click the Invite GroupCord button and choose "Open Link in New Tab" so you can continue following this guide while inviting the bot.
Visit:
Create a bot inside your GroupMe group.
Save your:
- GroupMe Bot ID
- GroupMe Access Token
Fork this repository to your GitHub account.
Visit:
Sign in using GitHub.
Click New Project.
Name it anything you'd like.
Example:
GroupCord
Inside your project:
Click Create Service
Choose:
From Git Repository
Select your fork of GroupCord.
Deployment Type:
Buildpack
Add the following Runtime Variables:
DISCORD_TOKEN=YOUR_DISCORD_BOT_TOKEN
CLIENT_ID=YOUR_DISCORD_APPLICATION_ID
GUILD_ID=YOUR_DISCORD_SERVER_ID
GROUPME_ACCESS_TOKEN=YOUR_GROUPME_ACCESS_TOKEN
GROUPME_BOT_ID=YOUR_GROUPME_BOT_ID
PORT=3000Click Create Service.
Wait until the logs display:
π GroupCord is online!
Northflank will generate a public URL similar to:
https://groupcord-xxxxx.code.run
Copy the URL.
Return to:
Edit your GroupMe bot.
Set the Callback URL to:
https://YOUR-NORTHFLANK-URL/webhook/groupme/YOUR_GROUPME_BOT_ID
Example:
https://groupcord-abc123.code.run/webhook/groupme/325cf6495ff62383cae340bec9
Save your changes.
Inside Discord run:
/setup
Choose:
- Discord Channel
- GroupMe Bot ID
Press Enter.
π That's it!
Your Discord server and GroupMe group are now connected.
Send a message in Discord.
It should appear in GroupMe.
Send a message in GroupMe.
It should appear in Discord.
If both tests succeed, your bridge is working correctly.
GroupCord currently uses SQLite to store bridge configurations.
On Northflank's free plan, application storage is temporary.
This means that bridge configurations are reset whenever the application is redeployed, such as after pushing a new update from GitHub.
Don't worryβyour deployment, bot, and GroupMe configuration are not lost.
Simply run:
/setup
again for each bridge you want to reconnect.
This usually takes less than a minute.
Future versions of GroupCord will support persistent databases to eliminate this limitation.
| Command | Description |
|---|---|
/setup |
Create or update a bridge |
/bridges |
View all configured bridges |
/unlink |
Remove a bridge |
/status |
Check bridge status |
/ping |
Verify the bot is online |
Discord
β
βΌ
Discord Gateway
β
GroupCord
β
Express Web Server
β
βΌ
GroupMe Callback
This section is intended for developers contributing to GroupCord.
Clone the repository:
git clone https://github.com/camdaloon/GroupCord.gitInstall dependencies:
npm installCopy the environment file.
Windows:
copy .env.example .envLinux/macOS:
cp .env.example .envRun:
npm startIf testing locally, expose port 3000 with ngrok:
ngrok http 3000Then update your GroupMe callback URL.
Upcoming features:
- π Web Dashboard
- π³ Docker Support
- π Bridge Analytics
- π Better Emoji Support
- π Additional Attachment Support
- βοΈ PostgreSQL Support
- π Discord OAuth
- π³οΈ Voting System
See ROADMAP.md for the complete roadmap.
Contributions are always welcome!
Please read:
CONTRIBUTING.md
before opening a Pull Request.
This project is licensed under the MIT License.
See:
LICENSE
Coming Soon
- Discord β GroupMe
- GroupMe β Discord
- Images
- Replies
- Web Dashboard
Made by camdaloon