Ship WordPress from a Slack mention

Mention @SandyWP with a plugin .zip, a list of wordpress.org plugins, or a deploy <branch> command. It can spin up a fresh WordPress sandbox or install directly on one you are already testing, then replies in-thread with the URL and a magic login link.

Add to Slack Read the guide

Mention-based · no slash commands · bot tokens stored encrypted · deploys run as your account

Trusted by

One bot, the whole deploy loop

Everything below happens by @mentioning the bot in a channel it belongs to. Replies land in the same thread.

Create a site

Spin up a fresh WordPress sandbox from a mention. Optionally set a name so you can target it later with deploys and deletes.

@SandyWP create a site@SandyWP create a site name:plugin-test

Specific WP version

Use a stable release, beta, or shorthand such as 7.1. When one release matches, SandyWP selects it; when several match, the bot shows the exact choices.

@SandyWP create new site, name: future-test, wp: 7.1@SandyWP create new site, name: future-test, wordpress version 7.1 beta

Deploy a plugin ZIP

Attach a plugin .zip and mention the bot. It installs and activates the plugin, then replies with the site URL and a one-click magic login link. Say to my-demo to land it on a sandbox you already have.

@SandyWP create a site wp: 6.9 and install this@SandyWP install this to my-demo@SandyWP name: my-demo

Preinstall plugins by name

Name any wordpress.org plugins (up to 10) after install or with and they arrive installed and activated — alongside your own .zip in the same message. Mistype one and the bot says so before it builds anything: did you mean publishpress-authors?

@SandyWP create a site name: plugin-test, install this, and publishpress-authors, post-expirator@SandyWP create a site with query-monitor, woocommerce

Add plugins to a running site

Install and activate up to 10 wordpress.org plugins on a sandbox you are already testing. Separate slugs with commas or and, name the site directly, or let SandyWP show your ready sites in the same button/dropdown picker used for Git deploys.

@SandyWP install query-monitor, woocommerce@SandyWP install publishpress-authors, post-expirator on my-demo

Deploy a git branch

No ZIP needed. Deploy a branch from a site’s connected repository — the branch overrides the repo’s default for that run only.

@SandyWP deploy development@SandyWP deploy branch main

Manage sites

List and delete sandboxes without leaving Slack. Deletes ask for a button confirmation first — nothing is removed until you click.

@SandyWP list my sites@SandyWP delete my-demo

Link your account

Deploys run as you — your account, your plan limits. Link once in the browser; unlink anytime.

@SandyWP login@SandyWP logout

Not sure where a deploy should land? If you already have ready sites, the bot posts buttons to pick one (or create a new site) instead of guessing.

Up and running in three steps

A workspace admin installs once. Everyone else links their account and ships.

Add to Slack

A workspace admin clicks Add to Slack and approves. Your bot token is stored encrypted — nothing to configure.

Invite the bot

Run /invite @SandyWP in any channel you want to use it in. It only sees channels it’s added to.

Link & deploy

Mention @SandyWP login to connect your account, then create a sandbox, deploy a ZIP, or install a wordpress.org plugin on a ready site.

Add to Slack

How account linking works

Deploys always run as your SandyWP account, against your plan limits.

Mention @SandyWP login. The bot replies in-thread with a one-time link.
Open it, sign in to SandyWP, and click Link my account. A personal API token is created just for Slack.
Deploys now run as your account, against your plan limits. Mention @SandyWP logout to revoke the token and unlink anytime.

Links are single-use and expire after ~10 minutes. Bot tokens and API tokens are stored encrypted at rest (AES-256-GCM).

Deploy without leaving the conversation.

Add SandyWP to your workspace and ship a plugin in the next reply.

Add to Slack Read the guide