Sorties: Fire Real Actions Straight From Your AI Chat

You are in a chat with your AI, and you just decided something needs to happen. A bug needs fixing. A teammate needs the news. An automation needs to run. Normally that is where the chat stops and the busywork starts. Open the dashboard. Find the button. Log in again. Do the thing.

A Sortie kills that detour. You set the action up once. After that you just say it in the chat, and it happens.

What a Sortie is

A Sortie is a saved action your AI can fire for you, by name, from inside a chat.

It always points outward, at a tool that lives outside BlackOps. Anything with a webhook qualifies: a Slack channel, a Zapier or Make automation, a Claude routine, your deploy pipeline, a script running on your own server. The jobs BlackOps already handles for you, like publishing a post or sending a tweet, are built in. You don't need a Sortie for those. A Sortie is how you reach the third-party tools BlackOps does not own.

You wire it up once, then fire it by name:

Fire the bug-fixer sortie.

You never paste a key into the chat. The conversation never sees it. And because the key lives on the server instead of your laptop, you can fire from your phone, the web, or a borrowed computer.

Example 1: Fix the bug

This is the Sortie I built first, because it scratched my own itch.

I keep a running list of bugs in BlackOps. When I want one fixed, I don't open my editor. I fire the bug-fixer sortie and pass it the bug:

Fire the bug-fixer sortie on the quote-tweet 403.

That message is the payload. It is how the sortie knows which bug to go after, by ID or by description. On the other end, a coding routine picks up that bug, traces it through the code, and writes the fix. I can have it watch the pull request, merge it, and report back when the fix is live.

I have done this from my phone, in bed. Fire it, put the phone down, wake up to a merged fix.

The bug-fixer routine mid-run. It reads the bug I just logged, fetches the note, digs through the render pipeline, and starts on the fix. This particular run is repairing a real bug in the very demo clips you are watching in this post.

The point is not that I can fix bugs. The point is I can start the fix from anywhere, in one sentence, without sitting at my laptop.

Example 2: Tell the team

Here is one almost everyone needs.

You are deep in a chat. Planning a launch. Finishing a draft. Making a call. The team needs to know. Instead of switching to Slack and retyping it, you fire a Sortie that posts to your channel and pass it the message you want sent:

Fire the team-update sortie: Landing page is live. Links are in the doc.

It lands in Slack for everyone, instantly. Same move works for Discord, Teams, a customer email, or a text to yourself.

Example 3: One sentence, a thousand tools

This one changes how you work.

If you use Zapier, or Make, or n8n, you already have little automations wiring your apps together. Zapier alone connects to roughly 6,000 of them. A Sortie fires any automation you have set up there.

So one sentence in chat sets off a whole chain you built once and never touch again. You fire the sortie and pass it the details:

Fire the new-lead sortie: Acme Co. Sounds keen. Follow up Tuesday.

Behind that one line, your automation can add Acme to your CRM, drop a row in a Google Sheet, create the follow-up task in Notion, and send a welcome email. All at once. You never open Zapier. You never see the wiring. You say the words and your tools light up.

A few more that write themselves, all of them third-party tools reached by webhook:

• "Fire the deploy sortie" and your latest changes ship to production.
• "Fire the invoice-paid sortie" and it hits your accounting app, pings your bookkeeper, and sends a thank-you.
• "Fire the standup sortie" and yesterday's updates land in the team channel as a clean summary.

If you can say "when this happens, do these five things," you can fire it from chat as a Sortie.

Setting one up

You arm a Sortie once, in BlackOps settings. It takes about a minute.

• Name it. This is what you fire later, like bug-fixer or new-lead.
• Paste in the webhook URL the other tool gave you. Every service that supports this has one. Zapier calls it a catch hook, Slack calls it an incoming webhook, your deploy host calls it a deploy hook.
• Add the key or token that tool needs to let you in, if it needs one. BlackOps stores it write-only. You can rotate it, you can never read it back, and the chat never sees it.
• Save. The Sortie is now armed.

That is the whole setup. After that the Sortie lives in your chat, ready to fire by name.

How you use it

Two moves, both in plain chat.

See what is armed:

What sorties do I have?

Fire one, and pass it a message:

Fire the [name] sortie: [what you want it to act on].

That message is the payload. The bug ID to fix. The note to post. The lead to log. The Sortie hands it straight to the tool on the other end.

Your keys stay in the safe

The whole reason Sorties exists is to keep the dangerous part out of your chat. The passwords. The API keys.

You save a key once and BlackOps locks it away. You cannot read it back, and neither can the chat. It gets unlocked for the split second it takes to fire, then it is gone again. Every fire gets logged, so you always know what ran, when, and whether it worked.

You fire from anywhere, and your keys never ride along in a chat window.

Set it up once. Fire it from anywhere.

That is the whole promise. Take the things you do over and over. Fixing. Shipping. Telling people. Kicking off automations. Turn each one into a sentence you can say from your laptop, your phone, or a web chat on a borrowed computer.

The conversation is where you decided what to do. Now it is where you do it.

---

💌 Want more insights like this?

Subscribe to my newsletter for weekly deep dives into frontend development, AI, and productivity.