Set up integrations

Settings → Integrations holds the connections the whole workspace shares. Only admins see it. The page has three parts:

• Linear: where feedback reports go, and where their status comes from
• Slack app: the credentials behind personal Slack direct messages and Connect to Slack
• Slack channel: a webhook that posts a message to a shared channel whenever a new run arrives

Each person’s own notification choices are separate, under Settings → Notifications. See Configure notifications.

How secrets are stored

Data Hub encrypts the secrets you paste on this page before saving them: the Linear client secret and signing secret, and the Slack bot token and client secret. It never shows a saved secret again. To change one, paste a new value and save.

Encryption needs the INTEGRATION_SECRETS_KEY environment variable on the web app. It is 64 hexadecimal characters; generate one with openssl rand -hex 32, set it in Vercel, and redeploy. Until it is set, saving a secret fails, and the Slack app card says so.

If the key changes after secrets were saved, Data Hub can’t read them anymore. The affected field says Can’t read saved value. Put the old key back, or paste the value again and save.

Linear for feedback reports

Feedback that people send from Data Hub becomes an issue in your Linear workspace, and the report’s status follows that issue. Until an admin saves a Linear team here, the Feedback item stays out of the account menu, and sending feedback through the API or an AI assistant returns an error saying feedback isn’t set up. What reporters see is in Send feedback.

The Linear card walks you through four steps.

1. Connect your Linear app

Data Hub signs in to Linear as an app, so you create one app in Linear for it.

Data Hub checks the credentials with Linear before it saves them. If client credentials are turned off for the app, the card says so; turn them on in the app’s settings in Linear and choose Connect again.

If the credentials belong to a different Linear workspace than the one already connected, Data Hub asks before switching. Switching clears the team, project, labels, and signing secret. Issues already in Linear stay there.

2. Choose where reports go

Changing the team later clears the project and labels. Status updates also stop until the Linear webhook from step 3 points at the new team.

3. Get status updates from Linear

A webhook tells Data Hub when an issue changes, so it can update the report and tell the person who sent it when the issue closes.

Data Hub uses the signing secret to check that each update really comes from Linear. The step shows Waiting for an update from Linear until the first one arrives. Any change to an issue in the team sends one, including the test report in the next step.

4. Send a test report

Choose Send test report. Data Hub files a report as you and links to the new Linear issue. Move that issue to Done in Linear. The step confirms that the issue closed and that you got a Data Hub notification. You can also skip the test.

After setup

Once setup is finished, the Linear card shows a summary: the connected workspace, where reports go, whether status updates are working and when the last one arrived, and what reporters see for each Linear status.

Data Hub notifies the reporter once, when the issue first closes. Moving an issue from one closed status to another, such as Done to Released, doesn’t notify again. Reopening an issue and closing it again does.

If Data Hub keeps rejecting updates from Linear, Status updates shows Not working. The usual cause is a wrong signing secret, or Linear turning the webhook off after repeated failures. Paste the signing secret again from the webhook’s page in Linear, and check that the webhook is still turned on.

Disconnect Linear turns feedback off. Issues already in Linear stay there.

Slack app for direct messages

Personal Slack direct messages and the Connect to Slack button use one shared Slack app. Create the app once in the Slack API portal, then give Data Hub its credentials. You can reuse an existing Slack app, including the one behind the channel webhook.

Create the app

Give Data Hub the credentials

Enter the credentials in the Slack app card under Settings → Integrations, or set them as environment variables on the web app. A value saved in the card takes effect right away, with no redeploy, and is used instead of the matching environment variable.

Each field shows where its value comes from: Saved here, Using followed by the variable name, or Not set. Remove saved value makes the environment variable the source again. If Data Hub can’t read a saved value, for example because INTEGRATION_SECRETS_KEY changed, it uses the environment variable in the meantime.

Two settings exist only as environment variables, and changing them needs a redeploy:

Members can then connect under Settings → Notifications. Deploy runbooks are linked from Deploy Data Hub.

Slack channel for new runs

The Slack channel card holds a Slack incoming webhook. Data Hub posts one message to that channel each time a new run is reported. This is separate from personal direct messages, which each person turns on for themselves.

To change channels, paste a new webhook URL. To stop the messages, remove the webhook. This setting has no environment variable.