Integrations
Slack and messaging
Start a run from the conversation where the request already has context, and get the result in the same thread.
Most requests are born in a conversation. Someone describes a problem in a channel, and the context that makes it answerable is the eight messages above it. Starting the run there keeps that context attached instead of asking someone to restate it.
What Slack can do
- Start a run by tagging Opulent in a thread, with the thread as context.
- Trigger an automation from a message or a reaction.
- Receive status, completion summaries, and the artifacts a run produced.
- Carry a question back when the run needs a decision, in the thread it started in.
- Return an answer to a plain-language question against a connected database.
When the run needs approval, it asks where the person already is. A question in the thread gets answered. A question in a dashboard nobody opened does not.
Scoping channel access
An automation names the Slack channels a run may use. Scope that to the channels the workflow belongs in, both so the run cannot post somewhere unexpected and so a noisy channel cannot start work that nobody asked for.