CHATBOTS

Slack /deploystatus Read-Only Deploy and Flag Auditor

Ask /deploystatus <project> in Slack to get the current live Vercel deployment, the commit it points to, and every recent flag toggle and rollback from the audit log.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerchat
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSomeone runs /deploystatus <project> in SlackSlack
  • ActionRead active Vercel deployment + commitVercelVercel
  • ActionEnrich commit with GitHub author + messageGitHubGitHub
  • ActionQuery recent toggles + rollbacks from PostgresPostgreSQLPostgres
  • OutputPost read-only deploy snapshot to SlackSlack

What it does

Gives anyone a one-command answer to "what's live right now and what changed?" `/deploystatus web-prod` returns the currently promoted Vercel deployment, its commit SHA and author from GitHub, and the last several flag toggles and rollbacks pulled from the Postgres audit table — all in a single Slack reply. It changes nothing; it only reports.

When to use it

Use it during an incident or a handoff when you need ground truth without poking production. Support, PMs, and on-call can self-serve the current deploy state and recent operational changes instead of pinging an engineer.

How it works

  1. 1Someone runs `/deploystatus <project>` in Slack (trigger).
  2. 2The bot reads the active Vercel deployment and its source commit.
  3. 3It enriches the commit with author and message from GitHub.
  4. 4It queries Postgres for the most recent flag toggles and rollbacks on that project.
  5. 5It assembles a single snapshot card — live URL, commit, deployed-at, and a recent-changes list.
  6. 6It posts the read-only summary back to the channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect VercelDeploys, runtime logs, analytics.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect PostgresAny Postgres URL — query, write, migrate.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.