Slack threads: Polylane reads channels, posts and replies
Polylane reads and posts in Slack
Polylane threads can read your Slack channels and threads, post and reply, react and upload files, for teams that discuss production problems in Slack.
What changed
Threads can work in your Slack workspace. Polylane lists the channels it can see, reads channel history and thread replies, posts messages and thread replies, reacts to messages and uploads files such as logs and images.
Replies where the conversation is
Polylane can read a Slack thread for context and reply inside that same thread, so what it finds lands next to the discussion it came from.
More of
Vercel in the context graph
Vercel syncs now bring in each project's aliases, certificates, custom environments, DNS records, firewall configuration, log drains, storage, installed integrations and webhooks, so investigations see how a project is wired up beyond its deployments.
Why it matters
Production problems are usually discussed in Slack before anyone opens a tool. When Polylane can read that discussion and answer in the same thread, the people already talking about the problem get the findings where they are, and nobody has to paste context from one place to another.
How to use it
- Connect
Slack under Settings > Integrations in the console. Connecting creates
#polylane-notificationsand invites you to it. - Invite Polylane to a channel, then mention it in a message, for example "@Polylane why are checkout requests failing since 14:00?".
- Reply in the same
Slack thread to continue. The thread also appears under Threads in the console.
Related
Improvements
- Pull requests When Polylane opens a pull request with a fix, every member gets an email and your Slack channel gets a post with a link to it
- Pull requests A fix that fails is reported by email and in Slack too