Connect your tools
Send what happens in bynh to the chat, issue tracker and on-call tools your team already watches, or to your own systems.
3 min readUpdated
Integrations send events from your workspace to other tools: a monitor going down, a new disclosure report, a certificate about to expire. Each connection picks the events it wants, and rules can narrow them further. Integrations are included in every workspace; you get events for the layers you have.
Every integration
| Kind | Tools | What it does |
|---|---|---|
| Chat | Slack, Microsoft Teams, Google Chat, Discord, Telegram | Posts a message to one channel, space or group. |
| Issue trackers | Jira, Linear, GitHub Issues | Opens an issue for a report or incident, comments on it as things change, and reads its status back. |
| On-call | PagerDuty, Opsgenie | Opens an alert when a monitor goes down or an incident opens, and resolves it when it’s over. |
| Webhooks | Signed webhooks | Sends signed JSON to any public https endpoint: your own service, Zapier, Make or n8n. |
Each tool can be connected up to 10 times in a workspace, so you can post to several channels, file into several projects or send to several endpoints. Email notices are set per person in Settings › Notifications; see Get notices by email.
Connect one
Step 1: Open Integrations
Go to Settings › Integrations and pick a tool. Its card says whether it’s connected and how its last delivery went.
Step 2: Sign in or paste a key
Slack, Jira, Linear and GitHub connect with one click (Add to Slack, Connect Jira, Connect Linear, Connect GitHub), so there’s no key to copy. You can paste a webhook URL, token or API key instead. The other tools take a webhook URL or key; the connect sheet shows where to find it.
Step 3: Pick the events
Under What should we send?, choose events by group: Status page, Certificates, Disclosure, and Access and policies. To narrow them, add a rule under Only send when; see Route events with rules.
Step 4: Send a test and save
Choose Send a test to check it before you save, then Save connection. The test shows in the tool as “bynh is connected”.
What a connection shows
| Status | Meaning |
|---|---|
| Delivering | Events are going through. |
| Needs attention | The last delivery failed. bynh keeps trying the next ones. |
| Turned off | Five deliveries failed in a row, or the tool removed bynh’s access, so bynh stopped sending. |
| Paused | Someone paused it. Nothing is sent until it’s turned back on. |
Messages are written in your workspace’s main language, English or Arabic. Saved keys and webhook URLs are stored encrypted, and only their last 4 characters show after you save. bynh only calls public https addresses, never private networks, and doesn’t follow redirects.
Disconnect
Open the connection and choose Disconnect. bynh deletes the saved address and keys and stops sending; the delivery log stays for 90 days. For a connection you added with one click, also remove bynh in the tool itself if you no longer want it there. bynh links you to the right page.
Was this helpful?