Skip to main content
Mention @SandyWP in an invited Slack channel to create a sandbox, deploy a plugin ZIP, install directory plugins, or deploy a Git branch. The bot replies in the thread with the result and a login link when the action succeeds. A workspace administrator installs the app once from the SandyWP for Slack page or the Slack tab in the account area. Then invite the bot to each channel where people should use it.
Open the one-time browser link from the login reply and choose Link my account. Each Slack user links their own account, so actions use that user’s sandbox access and plan limits. Use @SandyWP logout to revoke the link. Login links are single-use and last about ten minutes.

​
Deploy a plugin ZIP

Attach a plugin ZIP and mention the bot. The wording determines whether SandyWP creates a sandbox or targets an existing one. The picker belongs to the user who started the command and expires after about 15 minutes. If the ZIP appeared earlier in the thread, reply with @SandyWP upload that plugin to select the latest ZIP.

​
Install directory plugins and deploy branches

Install up to ten WordPress.org plugins on a new or existing sandbox.
Plugin slugs are checked before a sandbox is created. A typo returns suggestions instead of silently creating an incomplete site. Deploy a branch only after connecting a repository in Git deployment.
When several ready sandboxes have repositories, Slack offers a repository-only picker. A ZIP attachment takes precedence over a branch deploy command.

​
Site commands

Deletion always needs a button confirmation. Use @SandyWP help when you need the full command list.

​
Troubleshooting and privacy

If the bot does not respond, invite it to the current channel. If a picker has expired, resend the command to receive fresh controls. Plugin ZIP uploads are limited to 50 MB; use Git deployment for larger projects. SandyWP encrypts the workspace bot token and your linked API token at rest, and unlinking removes the saved account mapping.