What shipped: approve from Slack, REST, n8n, or Zapier

The approval used to live on your phone and in the dashboard. Now it can land where you already work. This release adds four channels for the same thing: a person says yes or no before an agent does something it cannot undo.

Approve from Slack

Agent and Agent Pro plans get Slack DM delivery, so the question shows up in your DMs and you tap through to answer. Team tier adds inline Slack approvals built on Block Kit: the approve and deny buttons render in the message itself, and every request is checked against Slack's signing secret before Pushary acts on it. No copy-pasting a link, no leaving the channel. The inline buttons are one-tap approve or deny; to send a reason back to the agent, open the question on the phone app or the web. The answer source gets written to the audit trail as "Slack" so you can see later who approved what and from where.

Ask a human from any backend

There is a REST endpoint, /api/v1/server/ask, that does one job: post a question and block until a human answers or it times out. Any backend can call it. If you have an agent or a workflow that is not one of the CLIs we hook into, you can still gate a step on a real person. It is the same question-and-wait loop the MCP tools use, exposed over plain HTTP.

No-code with n8n and Zapier

A community n8n node and a Zapier integration wrap the ask endpoint, so you can drop a human approval step into a no-code workflow without writing the HTTP call yourself. Build a flow, add the Pushary step where a decision matters, and the run pauses until someone responds.

Turn it on

Slack lives under the Connections tab in settings. The REST endpoint takes your API key. The n8n and Zapier steps ask for the same key. Slack inline approvals are on Team tier; DM delivery is on Agent and Agent Pro. The quickstart covers setup, and /ai-agents has the full picture of what the control panel does once a person is back in the loop.