Slack integration
Approve headcount requests in Slack. Kinnect keeps the record.
A budget owner acts on a position request where the conversation is already happening. The approval chain, the required comment and the position History do not change; only the surface does.
Standard APIs. Your Collaboration stays the system of record for what it owns.
Slack and Kinnect connected: Position request notifications and approval actions, both directions; Requisition deep links shared in channels, outbound from kinnect; Approve / Deny with required comment, both directions.
What moves
What moves, which way, and who stays the record
Into Kinnect
- Position request notifications and approval actions
- Approve / Deny with required comment
Out to Slack
- Position request notifications and approval actions
- Requisition deep links shared in channels
- Approve / Deny with required comment
Who stays the record
Kinnect remains the record of every approval, comment and position History, whichever surface the approval happens on. Slack carries the conversation and the click; it never becomes the audit trail.
| Data | Direction | System of record |
|---|---|---|
| Position request notifications and approval actions | Both directions | Kinnect |
| Requisition deep links shared in channels | Outbound from Kinnect | Kinnect |
| Approve / Deny with required comment | Both directions | Kinnect |
What it does
Slack and Kinnect, on one position
- Approve where the conversation isA position request, backfill or change reaches the approver in Slack. Approve or Deny there with the required comment, and the decision is recorded in Kinnect exactly as it would be from the Inbox.
- The Inbox, still the recordEvery approval, whichever surface it happened on, lands in the approver's Inbox history and the position's History with its comment. The Dashboard Approvals card shows what is still waiting and for how long.
- Requisition deep linksA requisition deep link opens the req modal directly (the URL carries the requisition id). Paste it in a channel and the reader lands on the requisition, not on a login page followed by a search.
The Kinnect record Slack connects to: a position request awaiting approval in the Inbox
Setup
How setup works
Connect Slack from the Collaboration card in Settings > Integrations.
Approvers receive position request notifications in Slack and act on them there or in the Inbox.
The approval chain, budget owner assignment and required comment stay as configured in Settings.
Nothing about the chain moves to Slack. The decision, its comment and the History are written in Kinnect.
Kinnect Settings, Integrations: Slack connected under Collaboration
Who uses it
One integration, three teams
Finance
Budget owners approve in Slack or in the Inbox, with the required comment landing in the History either way.
HR and HRIS
HR sees every approval and its comment in one place regardless of where the approver clicked.
Recruiting
Recruiters share a requisition deep link in Slack and the reader lands on the req modal directly.
See it live
See Slack connected on a live workspace
Tell us how Slack is set up and how a seat moves today. We will show one approved, funded and in Slack, and the number that results.
- Thirty minutes
- Demo data, shaped by your requirements
- No obligation
A Kinnect position request at the approval step, with the approver's required comment recorded against the decision
Slack integration questions
Is the Slack integration available?
Yes. Connect it from the Collaboration card in Settings > Integrations.
How do approvals work with Slack connected?
The approver can act in Slack or in the Inbox. Either way it is Approve / Deny with a required comment, recorded in the position's History.
Can I share a requisition in Slack?
Yes, with a deep link that opens the requisition modal directly.
Do Slack approvals bypass the budget owner?
No. The approval chain is the same; only the surface changes.
What about Microsoft Teams?
Listed on the integrations hub as planned; there is no page yet.
See an approval land in Slack
A demo shows a request arriving in Slack, the required comment, and the History it lands in.