On this page
Automations
Automations connect your boards to Slack and Sentry, in three parts:
- Slack automations post board moments to a channel as they happen, and a briefing of the week's changes on a schedule.
- 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.
Before you start
An owner or admin connects your organization's Slack workspace once, in Settings → Connectors, and for Sentry insights adds a Sentry API key there. The whole organization shares both connections. See Integrations Reference.
Slack automations
Needs the Pro plan or above. On a plan without Automations, existing automations stop posting but stay in place, and start again when you upgrade.
An owner or admin sets these up in Workspace settings → Automations. Each automation posts the moments you choose to one channel.
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 to post about:
Create it and send a test
Click Create automation, then Send test on its row to check that the message reaches the channel.
Each post links back to the board, work item or insight. You can pause or delete an automation from its row; deleting it also deletes its post history, but messages already in Slack stay.
The Monday briefing
Changed 12 October 2026: the post names diary entries, each linked to its entry on the Changes screen.
The Monday briefing posts a briefing of the week's changes to the channel on a schedule. It is built from the root hub's diary. It covers the week that held the day one schedule interval before the post, which on the default schedule is the previous week.
The post opens with a headline: the top change, the systems that depend on it, and how many more need a look. Below it, up to three diary entries that hit a change rule, highest-ranked first, each linked to the entry on the Changes screen. It names the apps whose work hit no rule as Routine, gives the week's commits and the share naming a coding agent, and ends with Open the hub.
Workspace settings → Reporting → Briefing schedule sets when it posts: every so many days, on a weekday when weekly, at an hour in UTC. One schedule serves every automation in the workspace that has the moment ticked. See Reporting.
Recent posts
The list shows the last 50 posts and their status:
- Retrying: Slack was busy or unreachable. We retry up to six times.
- Failed: Slack refused the post, for example because the channel was archived or Slack was disconnected. Slack's reason shows under the message.
Share to Slack
Share to Slack posts once to a public channel, with an optional note. It works on every plan, from three places:
- A board: the board menu (⋯) → Share to Slack…
- A work item: its row menu → Share to Slack…
- An insight: the Slack icon in the header of an open insight.
A public board's post links to its published page, so people without a ProvenMap account can open it. Owners, admins and editors can share. Until your organization has Slack connected, the dialog says so, and Open Connectors takes you to Settings → Connectors, where an owner or admin connects it.
From Chat
In Chat, ask: "post this board to #architecture and say the payments split is ready for review". ProvenMap shows you the exact message and the channel first, and posts nothing until you approve.
Sentry insights
Needs the Pro plan or above.
Connect a project
With the Sentry API key added in Settings → Connectors:
- Open the app board's hub and choose Bindings → Add → Create New → Browse Providers, then 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 both 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, and links to the issue in Sentry. Its priority:
The drafts are tagged sentry; review them like any other insight.
How the list stays current
Each hourly pull replaces the previous drafts, so an issue that stopped occurring or was resolved drops out. 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.
What's next
Last updated October 27, 2026