Is it possible to set up a chatbot that lets you DM a Zapier agent in Slack?

Hi ​@BlairAtPatreon,

Excellent question, I haven’t given that much thought before but totally see how it could be beneficial. One workaround I can think of is having your team-members create 1 person private channels and then you can configure the agent to work with those private channels. 

You can configure the agent to trigger on new message and respond within the private channel.

Hope this helps!

Please keep me posted if you can in fact DM the agent directly!

Thanks for your reply, ​@robintrainward! That’s too wonky of a workaround, but I do appreciate you offering it as an idea. 

Anytime :)

Hey ​@BlairAtPatreon 👋

It’s possible to trigger an agent from a webhook so maybe you could set up an app in Slack that would send a webhook to the agent whenever someone DMs it a question. 🤔 

With that approach you’d switch the agent to use a Catch Hook (Webhooks by Zapier) as its trigger, though would be best to test on a different agent so people can still use the current one while you’re testing this out. Then you’d need to set up the Slack app to send its events to the URL that’s provided in the Agent’s Catch Hook trigger. Check out Slack’s Events API documentation for details on how to configure it from their side: https://docs.slack.dev/apis/events-api/ 

If you give it a try, let us know how it goes! 

Thank you! I will!

yeah, you're basically asking for a Slack bot that forwards DMs to your Zapier agent and then shoots the reply back. totally possible, but the gotcha is Slack's event subscriptions and URL verification handshake.

honestly the cleanest workaround is to spin up a tiny Slack app with a bot token, subscribe to the `message.im` event, and pipe those DMs to a webhook that triggers your Zapier agent. you'll need a public endpoint to handle Slack's challenge request though. a cheap serverless function on vercel or cloudflare workers does the trick, it's like 20 lines of python or node.

the thing that usually trips people up is Slack's 3 second timeout for url verification. if your zapier agent takes longer to respond, you'll need to defer the reply with `chat.postMessage` rather than returning it in the http response. it depends on how fast your agent is.

are you handling any auth or just letting anyone in the workspace dm the bot?

The webhook route SamB described is the one that actually works, and the parts that trip people up are all on the Slack side.

Subscribe to message.im in Event Subscriptions instead of plain message, so you only receive DMs and not every channel the bot sits in. Slack sends a url_verification challenge first, and your endpoint has to echo that challenge value back or the subscription never turns on.

Slack also expects a 200 back within 3 seconds. An agent run takes longer than that, so acknowledge the event right away and post the answer as a separate chat.postMessage call. If you hold the response open until the agent finishes, Slack retries the same event and the person gets answered twice.

Ignore any event that carries a bot_id, otherwise the bot's own reply comes back in as a new DM and it starts talking to itself.

The last one is easy to miss: pass the Slack user id into the agent as the conversation key. Without it every DM looks like one long conversation and context from one person shows up in someone else's thread.

One more layer I’d add before putting this in front of the whole workspace: verify Slack’s signing secret on every event, key conversation memory by both workspace ID and user ID, and keep a short-lived event-ID store for deduplication. Slack retries aggressively, so “return 200 fast” prevents some duplicates, but an idempotency check is what makes the workflow safe when a webhook or downstream step is retried later. I’d also start with an explicit user/channel allowlist and log the source event ID beside the agent run so an unexpected answer can be traced without exposing the full DM transcript.

I’ve been wondering about this too. Using a Zapier Agent inside a Slack channel is useful, but being able to DM the agent directly would make the experience much more practical, especially for questions that shouldn’t be posted publicly in a channel. A Slack app or bot-based workaround sounds like the most likely approach if direct messaging isn’t supported natively yet. I’ve also been collecting useful automation and workflow references on ngabquest.com, so I’m interested to see if anyone here has already built a working setup for this.

One detail worth flagging before you build the Slack app route: the Catch Hook trigger cannot complete Slack's URL verification on its own. Slack expects the endpoint to echo back the challenge value it sends, and the Catch Hook answers with its own JSON instead. That is the wall most people hit on step one, and it is why the answers here keep landing on a small function in the middle.

If you would rather not run any code, there is a no-code path that gets most of the way. Slack's Workflow Builder has a webhook step, so you can publish a workflow that opens a short form, collects the question, and posts it to your agent's Catch Hook URL. People start it from a shortcut inside their own DM with the bot, so it feels private even though there is no custom app behind it, and there is no public endpoint or verification handshake to deal with.

Either way, pass the Slack user id through with the question. The agent's reply comes back as a later step, and without that id there is nothing to route the answer to. The Send Direct Message action takes the user id directly, so the whole round trip stays inside one Zap.