Last updated September 25, 2026
Automations
Automations post board moments to Slack and turn Sentry issues into insights, for the many people who read Slack but never open a board. A channel gets a post when something changes, and your Sentry issues appear on the app they hit.
There are three parts:
- Slack automations post board moments to a channel as they happen.
- Share to Slack posts one board, work item or insight to a channel when you choose.
- Sentry insights turn new and regressed Sentry issues into insights on the app they hit.
Slack automations and Sentry insights are on Pro and above. Share to Slack is on every plan.
Before you start
An owner or admin connects your organization's Slack workspace once, in Settings → Connectors. For Sentry insights, they also add a Sentry API key there. The whole organization shares both connections. See Integrations Reference.
Slack automations
An organization owner or admin sets these up in Workspace settings → Automations. Each automation pairs one channel with the moments it posts about.
Pick a channel
Click Post to a Slack channel and choose a public channel. We post as the ProvenMap app, so it doesn't need to be invited first.
Choose the moments
Tick the moments this channel should get a post for:
Create it and send a test
Click Create automation, then Send test on its row. When the test message appears in the channel, the connection works.
Each post is a short card with a button back to the board, work item or insight. You can edit, pause or delete an automation from its row. Deleting it also deletes its post history, but messages already in Slack stay there.
Recent posts
Below your automations, Recent posts lists the last 50 posts and how each went:
- Sent: the post is in the channel.
- Retrying: Slack was busy or unreachable. We retry up to six times, with growing delays, within Slack's rate limits.
- Failed: Slack refused the post, for example because the channel was archived or Slack was disconnected. Slack's reason shows under the message.
If your organization moves to a plan without Automations, your automations stop posting but stay in place. They start again when you upgrade.
Share to Slack
Share to Slack posts one thing to a channel, once, with an optional note from you. It creates no automation and works on every plan.
You'll find it in three places:
- A board: the board menu (⋯) → Share to Slack…
- A work item: its row menu → Share to Slack…
- An insight: the send icon in the header of an open insight.
Choose a public channel, add a note if you want, and click Share. A public board's card links to its published page, so people without a ProvenMap account can open it.
Owners, admins and contributors can share. The action appears only when your organization has Slack connected.
From Chat
Ask Chat to share something: "post this board to #architecture and say the payments split is ready for review". Chat shows you the exact message and the channel first. Chat posts nothing until you approve, and sends nothing if you decline.
Sentry insights
Sentry insights show your runtime problems on the board, attached to the app that has them.
Connect a project
- An owner or admin adds your Sentry API key in Settings → Connectors.
- Open the app board's hub and choose Bindings → Add → Add Source → Import from a connector → Sentry.
- Pick your Sentry organization, then the project that belongs to this app.
What becomes an insight
Every hour, we read the project's unresolved issues from the last day. An issue becomes a draft insight when two things are true:
- It is new (first seen in the last seven days) or came back (Sentry marks it regressed or escalating).
- It has at least 10 events or affects at least 5 users.
We file up to 10 per project, the issues affecting the most users first.
The insight sits on the app's node, on the board above the app board. It carries the issue's title, its event and user counts, and a link to the issue in Sentry. Its priority follows how severe the issue is and how many users and events it has:
The insights arrive as drafts, tagged sentry, for you to review like any other insight.
How the list stays current
Each hourly pull replaces the drafts from the previous one, so an issue that stopped occurring or was resolved drops out without any action from you. Once you review an insight, it stays, and we don't file that issue again.
If a Critical or High issue arrives and a channel has High-priority insights ticked, that channel gets a post about it too.

