Integrations

Integrations connect Hark to the tools your team already uses. Each integration stores its credentials encrypted and is configured in Settings by an Admin or Owner.

GitHub

The GitHub integration links your engineering work to your customer operation, two ways at once.

• Development signals. Commits, pull requests, and branches whose message, title, or name contains a work-item key (for example, ENG-12) attach to that item and show on its development panel, including pull-request state (open, closed, or merged).
• Two-way issue sync. A conversation or work item can be linked to a GitHub issue. Replies flow to the issue as comments, resolving on one side mirrors to the other, and closing or reopening the issue on GitHub reflects back into Hark.
• Actions from an item. You can create a branch or open a pull request straight from a work item.

GitHub is connected as an app installation, and its webhook is signature-verified (see the developer webhooks doc for the technical detail).

Gmail

The Gmail integration brings inbound email support into the inbox. Connected mail is ingested into conversations, so an email to your support address becomes a conversation your team works like any other, and replies send back out. Note that Gmail ingestion is poll-based: Hark checks for new mail on a schedule rather than receiving a push, so there is no webhook to configure for it.

Slack

The Slack integration lets flows and automation send notifications into Slack, so your team can be alerted where they already work (for example, a Slack notify action on a flow that fires when an SLA timer goes critical).

Other integration types

Hark's integration model also recognizes types for Linear, Jira, Discord, Intercom, and Zapier. Availability of each depends on your plan and setup; GitHub, Gmail, and Slack are the primary supported integrations today.