How we handle GDPR data-subject requests on a deadline
Legal
A single agent reachable from Slack, with scoped access to our database, Stripe, Linear, and GitHub. Ask in a thread and it runs the task across whatever platforms it needs.



Operations work usually spans several platforms: the database, Stripe, the sandbox providers, Linear, and GitHub. Onboarding a customer means provisioning, setting up billing, and filing a tracking issue. Shipping a fix means reviewing a PR, cutting a branch, and updating a ticket. No single tool covers the whole task, so the coordination falls to a person moving between several tabs.
We run these tasks through a single agent reachable from Slack, with scoped access to the platforms we've connected. This is how we run our own operations on Kortix, and the same setup works for any team.
The cross-platform tasks are the ones no single tool owns. "Onboard this enterprise account" touches the database, Stripe, and Linear. "Get this fix out" touches GitHub, the sandbox that reproduces the bug, and the ticket that tracks it. Each step is simple; stitching them together means switching between tabs, copying IDs, and keeping the order straight.
The common workarounds each fall short. Internal scripts each do one thing and break when an API changes. A no-code automation tool handles the flow it was built for and nothing beyond it. A chatbot that integrates with Slack can answer questions but can't run a multi-step task, because it has no safe way to hold credentials and take actions across systems.
Our Slack is wired to an agent with scoped access to every connected system. You @-mention it in a thread and describe the task in plain language. It spawns an isolated session, a cloud sandbox, with scoped access to the platforms we've connected, works out the steps, runs them, and replies in the thread as it goes. Adding a capability means connecting one more platform.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the operations skill and the hourly health check, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a Slack control-pane agent in this workspace.
Create the agent agents/slack-control-pane.md. Its job is to run cross-platform operations tasks when someone @-mentions it in a Slack thread, and to reply in that thread. It may use the Linear and Stripe connectors and the GH_TOKEN and DATABASE_URL secrets.
Create the skill skills/control-pane-ops/SKILL.md with these rules:
Add a cron trigger control-pane-heartbeat to kortix.yaml. It runs the slack-control-pane agent every hour with the prompt "Load the control-pane-ops skill and run the health check. Post any failure to #ops."
Tell me which of these connectors and secrets are not set up yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Stripe and Linear. Add a GitHub token and a read-only database URL as secrets, and connect Slack as a channel so a mention reaches the agent. Connector credentials are brokered server-side and never enter the agent's machine.
Looks up plans and invoices, and refunds only after approval.
Reads PRs, issues and checks, and opens PRs without merging.
Merge the change request, then start a session with the slack-control-pane agent and send this prompt. It runs the health check by hand, so you see each credential work before the first real task.
Run one health check across every connected platform.
The change request added this heartbeat to kortix.yaml. It runs every hour
and only checks that each credential still works. The real work starts when
someone @-mentions the agent in a Slack thread, and each mention runs in a new
session on its own cloud computer. To change the interval, edit the cron line,
or open Triggers in the workspace.
triggers:- slug: control-pane-heartbeat name: Control-pane health heartbeat on: cron: "0 0 * * * *" run: agent: slack-control-pane prompt: Load the control-pane-ops skill and run the health check. Post any failure to #ops.Lookups, Linear issues and new pull requests run on their own. A Stripe refund, plan change or cancellation, or any access change, stops in the thread: the agent posts the exact change and waits for an explicit reply. It never acts on silence. Database writes never run, because the role is read-only, so the agent hands the statement to a person. A person merges every pull request.
Each run ends with one line per platform, and an alert in #ops if one fails. This is what a run looks like in the session:
The database, Linear and GitHub answered. Stripe returned 401, so the connector needs reconnecting. Posted 1 alert to #ops.
Once it works, paste any of these into the same session.
When someone writes onboard and an account name in a thread, look up the account, file the Linear project, and hold the Stripe plan change for approval.
Every morning at 09:00, post the Stripe invoices that failed in the last 24 hours to #ops, with the plan for each.
When a thread reports a bug, reproduce it in a sandbox, then file a Linear issue with the steps and the result.
Giving one agent access to the database, Stripe, sandboxes, Linear, and GitHub is a security question. The controls that make it workable:
Cross-platform tasks such as onboarding, reviews, provisioning, and billing changes now run in the Slack thread where they're already discussed, with the risky steps held for approval. Extending the system means connecting the next platform.