Comms
Slack
Read and post in Slack, as the workspace's bot or on a user's behalf.
Official site: slack.com
What it does
- Read and post messages in channels and threads
A workspace can scope this to a bot token, a specific user's token, or both. Sending or reading on someone's behalf is easy to over-scope; the right default is exactly what the task needs, no more.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Slack once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that — so nobody is blocked and nobody is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Slack at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Slack returns something usable instead of something generic.
Processes that run on Slack
Call feedback becomes tickets and docs
Every call recorded during the day is distilled overnight, with bugs and feature requests routed to the right team as tickets and docs, plus a Friday digest.
CRM hygiene and prospect job changes
Duplicates merged and broken fields repaired on a weekly schedule, with prospects who changed employer followed to their new company and a recap posted to the team.
Find buyers engaging with competitors
Everyone who engages with a competitor's posts gets found, scored against your ICP, enriched, and staged for outreach with a human approving the list.
Keep your knowledge base current
Every morning, the previous day's activity gets read across your team's tools and synthesized into what changed, automatically and unattended.
Merged PRs move tickets and post a digest
Every pull request that lands gets matched to its ticket, moved forward on the board, and rolled into one summary for the team.
Outreach based on Slack membership
Membership in a Slack community is the qualification, so everyone in it is in scope, resolved by name and corroborated against their own words.
Prepare for a customer call
Before the call, the last conversations, the account's state, how the product is actually being used, and where their requested features stand, in one brief.
Prepare for a demo from the last call
The last calls, the deal's state, and fresh research become one prep brief, plus a deck built around that company's own use cases, posted before the meeting.
Publish the Monday brief
Product usage, pipeline, and customer feedback joined into one executive report, published before the team sits down.
Revive deals that went cold
Deals lost more than 90 days ago come back with fresh signals, contacts checked for job moves, and the features they asked for that have since shipped.
Triage and route bug reports
An incoming report is read, matched against open issues to catch duplicates, and filed to the right team's board with severity attached.
Turn website visitors into outreach
Every company that reads your site gets one decision, and the few worth answering arrive as a named person with a note already written from the page they read.