Slack automation with approval
Slack automation for work that needs a judgment
Tell Kipwise Agent in plain words what should happen, and when. It asks you once, then runs on a schedule or when something happens in a connected tool. Every change a person asks for live waits for an Approve card.
7-day trial on install. No card needed.
@Kipwise when a row is added to the Signups sheet, draft a welcome email to that person
I’ll watch the Signups sheet and save a draft welcome email for each new row. You approve this once, now.
Draft a welcome email for every new row in the Signups sheet?
Draft a welcome email for every new row in the Signups sheet?
✓ Approved by Imogen PriceWatching Signups. When a row is added to SignupsNext run: on the next new row
New signup: Priya Nair, Northwind. I saved a draft welcome email in your Gmail drafts. Nothing was sent.
looks good, send it
I’ll send the draft.
Send “Welcome to Northwind” to Priya Nair?
Send “Welcome to Northwind” to Priya Nair?
✓ Approved by Imogen PriceSent to Priya Nair.
Sample data
How it works
Three steps, all in the thread.
Say it
Describe it in a sentence
“Every Friday at 16:00”, or “when a row is added”. There is no canvas and no field mapping. The agent works out the steps each time it runs.
Approve once
A plain-sentence card
When you create a schedule or an automation, one card lists what it will do. Only you can press it, and it expires after 30 minutes.
It runs
On time, or when it happens
It re-reads the record with your own access first, never acting on the notification alone, and posts the result in the thread.
On a schedule
Approve it once, then it runs
Ask for a post every Friday or a check every morning. You approve the schedule when you create it, and its later runs do not ask again. A live request that changes something, such as sending an email, always shows a card.
Ask “what happened on the last run?” and it tells you, failures included.
@Kipwise every Friday at 16:00, post the unpaid invoices here
I’ll run this every Friday at 16:00 with your QuickBooks access.
Post the list of unpaid invoices in #finance every Friday at 16:00?
Post the list of unpaid invoices in #finance every Friday at 16:00?
✓ Approved by Declan MossScheduled. Every Friday · 16:00Next run: Friday 16:00
Unpaid invoices, 6 to 12 Nov: 4 invoices, $9,350 in all. The oldest is Northwind, due 28 Oct.
Sample data
The Approve card, in its four states
One plain sentence, one person who can press it, and a clock. Whatever happens, it says so in words.
Draft a welcome email for every new row in Signups?
Draft a welcome email for every new row in Signups?
✓ Approved by ImogenDraft a welcome email for every new row in Signups?
✕ Denied by Imogen, nothing was runDraft a welcome email for every new row in Signups?
Expired, nothing was runSample data
No canvas, no field mapping, no guessing what broke
An automation here is a sentence the agent stores when you approve it. Ask what happened and it tells you in words.
What people say about building one
“I’m probably not helping my business by spending hours debugging automations and mapping fields.”Reddit, December 2025
“moving from basic "if-this-then-that" logic to suddenly needing to understand JSON structures, mapping arrays, and debugging these super unclear error messages is hurting my brain a little.”Reddit, April 2026
“the error messages aren't always obvious to the non-technical user that I am.”Capterra, June 2026
What you say instead
Post the list of unpaid invoices in #finance every Friday at 16:00?
Sample data
When something happens
Start from eleven tools
Say it once and the agent tells you, or acts, each time it happens: a payment fails, a deal is created, an invoice is paid, someone books a meeting, a row is added to a sheet.
It reads the record back with your own access before it does anything, so an automation never acts on the notification alone.
Sample data
Why people look for this
“I’m probably not helping my business by spending hours debugging automations and mapping fields.”
With KipwiseNo mapping. You describe it in a sentence, and debugging is a question: “what happened on the last run?”
“…the error messages aren't always obvious to the non-technical user that I am.”
With KipwiseReplies are in plain language, and an automation that stops tells its owner in the thread.
What it is for
- Work that needs a judgment
- Summaries, drafts, record updates and follow-ups, where a person should see the change first.
- Eleven event sources
- Google Sheets, HubSpot, Intercom, Linear, QuickBooks, Stripe, Xero, Zendesk, Calendly, Cal.com and HiBob.
- Approved once
- A schedule or automation is approved when it is created. Live requests that change something show a card every time.
- Your access
- Each run uses the connected accounts of the person who created it, and costs that person’s credit.
What to ask it first
@Kipwise every Monday at 9, post last week’s search clicks here
It asks once, then posts the figures on schedule with the date range.
@Kipwise when a payment fails, tell me here
It reads the payment in Stripe first, then posts what it found.
@Kipwise when a row is added to Signups, draft a welcome email
It saves a draft each time. Sending still shows a card.
@Kipwise what are my automations?
It lists them, and you can pause or cancel any of them.
Questions
How is this different from a Zap or an n8n flow?
Those wire fixed steps across many apps. Kipwise Agent re-plans each run with a model, reads the record first, and asks you to approve the change. It is built for work that needs a judgment and an approval, not for fixed steps across hundreds of apps.
Is this a Zapier AI agent for Slack?
Not in the sense of wiring many apps together. If you search for a Zapier AI agent or a Zapier Slack integration, the difference is that Kipwise Agent handles work that needs a judgment and an approval: it is not a way to build arbitrary multi-app Zaps. You describe the job in Slack, it reads the record, and you press Approve.
Is this an n8n for Slack alternative?
For Slack work that needs a judgment and an approval, there is no flow to build or host: you ask in Slack. An automation starts from a schedule or from an event in the eleven tools listed here.
What is human in the loop automation?
Automation that stops for a person before it acts. Here the person is whoever asked: the Approve card says in plain words what will run and when, and only they can press it.
Does a scheduled run ask me every time?
No. You approve the schedule once, when you create it, and its later runs use that approval. A live request that changes something still shows an Approve or Deny card each time.
What can start an automation?
A schedule, or an event in one of eleven tools: Google Sheets rows, HubSpot, Intercom, Linear, QuickBooks, Stripe, Xero, Zendesk, Calendly, Cal.com and HiBob. It fires only for the account you connected.
What happens when a run fails?
Ask what happened on the last run and it tells you in words. When a job stops, its owner gets a notice in the job’s thread.
Is a human always in the loop?
For every live change, yes: the person who asked presses Approve. For a schedule or automation, the person approves what it will do once, and can pause or cancel it at any time.
What does it cost?
$10 per user a month, for at least 3 users. That includes $5 of AI credit per person and $2 per person of shared team credit every month. Add it to Slack and the free trial starts on your first message, no card needed.
Can it change things without asking?
No. Before it edits a page, updates a record or posts a message, it shows an Approve or Deny card in the thread. Only the person who asked can approve it, and the card expires after 30 minutes. A denied or expired card runs nothing.
Who can see what?
The agent works as the person asking. It opens only the pages, files and records that person can open, in Kipwise and in every tool they connect.
Can an admin switch it off?
Yes. A workspace admin can switch a whole service, or a single tool, off, so a listed ability may be off in your workspace.
Does it work in Microsoft Teams?
Yes. The same agent runs in Microsoft Teams, with the same tools, approvals, memory and scheduled tasks.