Approvals in the channel
A pack posts the proposed action into Slack with full context. A person approves, edits, or rejects it before anything writes to production.
Pack Foundry + Slack
Pack Foundry uses Slack as the place where AI proposes work and your team approves it, without writing anything until a person signs off. Pack Foundry connects to Slack through a one-click connection under its OAuth-partner model. Inside a workflow pack, Slack becomes the approval surface: when a pack drafts an invoice entry, a follow-up reply, or a ticket response, it posts the proposed action into the channel or DM you choose, and a person approves or edits it before anything writes. Notifications, handoffs, and the audit trail all run through Slack so the work stays where your team already is.
A pack posts the proposed action into Slack with full context. A person approves, edits, or rejects it before anything writes to production.
Workflows route items to the right person or channel, so the request lands with whoever owns the decision.
The pack posts what it did, what is waiting on approval, and what it flagged as an exception, on the schedule you set.
Every workflow runs in dry-run and shows the proposed action before it touches Slack. Sensitive steps queue for human approval, and every decision lands in an audit log. Slack connects with one click under Pack Foundry's OAuth-partner model. Built and maintained by MVP.dev.
Yes. Sensitive steps run in dry-run and post the proposed action to Slack for approval. Nothing writes to your other tools until a person signs off in the channel or DM you chose.
No. Slack connects with one click under Pack Foundry's OAuth-partner model. You do not bring your own client IDs or stand up an app.
Any pack can use Slack for approvals, routing, and status. Finance, sales, intake, support, and ops packs all post proposed actions and exceptions where your team already works.