Connect your team's tools
Connect Jira, Linear, Slack, Notion, Sentry and other tools so audits see your decisions, owners and incidents. Send audit results to Slack or Discord.
This page is for a workspace admin. Connectors give Veriom context that is not in your code: design decisions, owners, tickets, and incidents. Apps send audit results to your team's chat.
Before you start
- You have the Admin or Owner role in the workspace.
- You are signed in to Veriom in your browser. Connectors cannot be added with an API token.
- You can approve apps in the tool you want to connect.
Connect a tool in one click
- In Veriom, open Integrations and select the Connectors tab.
- Under Add a connector, click Connect on the tool's card, for example Connect Linear.
- Fill in any fields the form asks for. Google Drive asks for a Folder URL.
- Click Continue to Linear. The tool's own consent page opens.
- Approve every permission it asks for.
Veriom brings you back and shows Connected. It checks the access, then starts the first sync straight away. The card's status updates as the sync runs.
One-click connect appears only for tools whose Veriom app is set up in your environment. If you see token fields instead, paste a token from the tool.
What each tool gives Veriom
| Tool | What Veriom reads | Permissions it asks for | How you connect |
|---|---|---|---|
| Jira | Projects and issues | read:jira-work, read:jira-user, offline_access. Adds write:jira-work if you turn on Allow ticket creation | One click |
| Confluence | Pages and blog posts | read:page:confluence, read:blogpost:confluence, read:space:confluence, offline_access | One click |
| Notion | Pages you share with Veriom | The pages you pick on Notion's consent page | One click |
| Google Drive | Documents in the folder you name | drive.readonly | One click |
| Linear | Teams, projects, and issues | read | One click |
| Slack | Channels, users, and channel members. Never message content | channels:read, users:read | One click |
| Sentry | Projects, issues, and releases | org:read, project:read, event:read | One click for sentry.io. Paste a token for self-hosted Sentry |
| Datadog | Monitors, incidents, and teams | Set by the key you paste | Paste credentials |
| PagerDuty | Incidents, services, teams, and escalation policies | Set by the key you paste | Paste credentials |
| CircleCI | Projects and pipelines | Set by the token you paste | Paste credentials |
| Jenkins | Jobs, builds, artifacts, and deployments | Set by the token you paste | Paste credentials |
| Airbyte | Sources, destinations, syncs, and lineage from your own Airbyte workspace | Set by the credentials you give | Paste credentials |
Jira and Confluence share one Atlassian sign-in. Veriom uses the first Atlassian site that your approval covers.
For GitLab and Bitbucket, see Connect a repository. For AWS, Azure, and Google Cloud, see Connect your cloud.
How syncing works
Each connector syncs on its own schedule. You can change it under Automatic sync: every 15 minutes, 30 minutes, hour, 6 hours, 12 hours, or day.
| Default | Tools |
|---|---|
| Every 15 minutes | Jira, Sentry, Datadog, Linear, PagerDuty |
| Every 30 minutes | Confluence, Notion, Google Drive |
| Every hour | Slack, CircleCI, Jenkins, Airbyte |
The first sync reads the last 90 days by default. You can set any window from 1 to 365 days.
Veriom renews one-click access before it expires. If the tool stops accepting it, the sync fails and Diagnose says the provider no longer accepts the connection. Click Reconnect to fix it.
Reconnect or remove a connector
Each connected card has these buttons:
- Sync now: start a sync immediately.
- Pause and Resume: stop and restart scheduled syncs.
- Reconnect: approve access again. Veriom keeps the connector's history and revokes the old approval. Connectors set up with a pasted token show Rotate instead.
- Diagnose: check the connection and get a suggested fix.
- Revoke: delete the stored access and the sync state. Only an Owner can revoke.
When you revoke, Veriom also withdraws its access at Linear, Slack, Google Drive, Jira, and Confluence. Notion and Sentry offer no way to do that, so remove Veriom's app in their own settings too.
Send audit results to Slack or Discord
- Open Integrations and select the Apps tab.
- Under Add an app, click Add to Slack or Add to Discord.
- Pick the channel on the consent page and approve.
- Veriom shows Slack connected or Discord connected. Click Send test on the app to check the channel.
By default the app posts when an audit completes, when an audit fails, and when an automatic audit could not start. Veriom keeps only the channel's webhook URL.
If your environment has no Slack or Discord app set up, click Paste a webhook URL instead and paste an incoming webhook URL. To send events to n8n, Zapier, or your own service, choose Webhook. Veriom shows the signing secret once when you create it.
If something goes wrong
| What Veriom says | What it means | Fix |
|---|---|---|
| The consent was cancelled. Nothing was connected. | You closed or declined the consent page | Click Connect again |
| That consent link expired or was already used. | Consent links work once and expire after 10 minutes | Click Connect again |
| The consent finished in another browser. | You started in one browser and finished in another | Start again and finish in the same browser |
| Only a workspace Admin can finish this connection. | Your role changed during the consent | Ask an Admin or Owner to connect it |
| The provider did not accept Veriom's app in this environment | Veriom's app settings for that tool are wrong | Contact Veriom support. Trying again will not help |
| The provider could not be reached. | The tool's sign-in service is down | Try again in a few minutes |
connector_oauth_wrong_host | You started from a different address than the Veriom app | Open https://veriom.io (not www or a preview link) and connect from there |
See Troubleshooting for more codes.
Was this guide useful?
Your response stays in this browser unless you open a GitHub issue.