Communications · 36 pre-built actions
Slack integration with Nexus
Bring approvals and updates to where teams work in Slack. Slack events start runs directly, and message, user and channel actions keep people informed and in control.
Pre-built actions
What you can automate
36 pre-built Slack actions, grouped by what they work on.
36
PRE-BUILT ACTIONS
- 01Messages actions post updates and approval requests.
- 02Channels actions create and manage channels for incidents or projects.
- 03Users actions look up and manage people.
Workflow
How it fits into a Nexus workflow
Slack is a trigger source in Nexus. An event can start a governed run directly, and Slack steps then run as pre-built actions in the same workflow.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Slack API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Approval requests in Slack
A run posts an approval request, and the response continues or stops the workflow.
Incident channel
A new incident creates a channel and invites the on-call team.
Run notifications
Completed and failed runs post a summary to the owning team.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Slack connector questions
- Which Slack actions are pre-built?
- Nexus includes 36 pre-built Slack actions across Messages (12), Users (10) and Channels (14).
- Can Slack start a workflow?
- Yes. Slack is a trigger source, so an event can start a run directly.
- What if the operation I need is not pre-built?
- Use the Slack API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- ServiceNow connector
Incidents, changes and CMDB.
- Microsoft 365 connector
Teams, email and calendar.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Slack fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.