Slack Integration
Post project events to your team's Slack channels as they happen.
SixGrid can post to Slack when work moves: a tollgate is completed, a project changes status, a to-do is assigned, or a comment lands. It also runs two daily checks that alert the channel when a project stalls or a tollgate goes overdue. Posts go to a channel you choose, and every project can have its own channel, its own pause, or its own off switch.
Connecting Slack
An Owner or Admin connects the workspace once for the whole organization:
- Go to Settings, Integrations and click Add to Slack.
- Slack asks you to authorize SixGrid for your workspace. Approve it.
- Back in SixGrid, pick a default channel. Nothing posts until this is set.
- Click Send test message to confirm the connection end to end.
SixGrid can post to any public channel right away. To use a private channel, invite the SixGrid app to that channel in Slack first, then select it.
What Gets Posted
| Event | When It Posts | What the Message Says |
|---|---|---|
| Tollgate completed | A milestone is marked done | The milestone and project, who completed it, and days spent in the phase versus the target |
| Project status changed | A project moves between statuses (for example, idea to active) | The project, the old and new status, and who made the change |
| To-do assigned | A to-do is created with an owner, or reassigned | The to-do, who it's assigned to, the due date, and the phase it belongs to |
| Comment posted | Someone comments on a to-do | The author, the to-do, and a preview of the comment |
| Project stalled | Daily check: 14 days with no activity, and again at 30 | The project, how long it's been quiet, and an @mention of the project leader |
| Tollgate overdue | Daily check: 1 day past due, and again at 7 | The milestone, how overdue it is, and an @mention of the project leader |
Every message links back to the project in SixGrid. The stalled and overdue checks only count time that passes after you connect, so connecting Slack never floods the channel with alerts about old history.
Choosing Which Events Post
All six event types are on by default. An Owner or Admin can turn any of them off for the whole organization on Settings, Integrations. Turning an event off stops those posts everywhere; the other events keep posting.
Routing Posts by Project
By default, every project posts to the org's default channel. The Project routing table on Settings, Integrations shows every active project and lets an Owner or Admin point each one at its own channel, or switch its posts off entirely. A team channel per project works well when a project generates a lot of discussion; the shared default channel works well as a portfolio-wide feed.
The same controls live on each project's Settings page for anyone with full access to that project.
Pausing a Project
Two ways to quiet a project without touching the rest of the organization, both on the project's Settings page:
- Pause stops posts for 24 hours, 7 days, or until a date you pick, then resumes on its own. Useful during a messy data-entry session or a reorganization.
- Off stops posts permanently until someone turns the project back on.
Good to Know
- The sample project never posts to Slack and does not appear in the routing table, so demo activity stays out of your real channels
- Channel posts cover everyone's actions, including your own. The channel is a shared team feed, unlike email notifications, which skip your own actions
- The @mention in stalled and overdue alerts works when the project leader's SixGrid email matches their Slack account email; otherwise their name appears as plain text
- Each event posts exactly once, and the daily checks never repeat an alert they've already sent
- An Owner or Admin can disconnect Slack at any time from Settings, Integrations. Posts stop immediately, and you can reconnect whenever you like