Slack & Discord Notifications
Your translators are busy. You don't want to babysit a dashboard all day waiting for a locale to hit 100%. Connect Stringhive to Slack or Discord and let the notifications come to you.
How it works
You give Stringhive a webhook URL from Slack or Discord. When something happens in your Hive, Stringhive formats a message and posts it to that URL. No bots to host, no developer accounts to register, no OAuth dances. Just a URL.
Setting up Slack
- In your Slack workspace, open Apps from the sidebar and search for Incoming Webhooks
- Click Add to Slack and pick the channel you want notifications in
- Copy the webhook URL. It looks like
https://hooks.slack.com/services/T.../B.../...
Then in Stringhive, go to Settings > Integrations, click Add integration, choose Slack, paste the URL, pick your events, and save.
Setting up Discord
- In your Discord server, open the settings for the channel you want notifications in
- Go to Integrations > Webhooks > New Webhook
- Give it a name and copy the webhook URL
Then in Stringhive, go to Settings > Integrations, click Add integration, choose Discord, paste the URL, pick your events, and save.
Available events
| Event | What you get notified about |
|---|---|
string.created |
A new source string landed in your Hive |
string.updated |
Someone changed a source string's value |
string.deleted |
A source string was removed |
translation.updated |
A translator submitted or edited a translation |
translation.approved |
A translation was approved |
comment.created |
Someone left a comment on a string |
locale.completed |
Every string in your Hive is approved for a locale |
Subscribe to whichever ones make sense for your workflow. Most teams care about translation.approved, comment.created, and locale.completed. The string-level events are more useful if you have people editing source strings while translation is actively in progress.
Testing your integration
After saving, use the Send test button next to your integration. Stringhive fires a test ping to your URL and shows you the response. If it works, you'll see a message appear in your channel within a second or two.
If the test fails, double-check that you copied the full URL. Slack URLs end in a long random string; it's easy to truncate them.
Delivery log
Each integration keeps a log of its last 10 deliveries. Click the log icon on any integration to see recent delivery attempts, their HTTP status codes, and any error responses. This is where to look if notifications stop showing up.
Same retry policy as webhooks: up to 3 attempts, with backoffs at 5 and 30 minutes.
Multiple channels
You can add as many integrations as you like. Different channels for different event types, separate Slack and Discord connections, a #dev-translations channel and a #pm-updates channel, whatever you need. Each integration is independent.
One integration, many events
One integration can subscribe to as many events as you want. You don't need separate integrations for translation.approved and comment.created. Subscribe to both in a single one.