Connect Code by Zapier and Pressable to power AI-driven automation

Adds a domain to a site. Adding a bare domain like client.com also adds

Creates a copy of an existing Pressable site. Every run creates a new site, so a Zap that fires again makes another copy. Clones are staging sites by default, which aren't billable. Choosing Live creates a billable production site. The clone is still provisioning when this step succeeds, and Pressable emails the site owner when it's done.

Creates a new WordPress site on your Pressable account. Every run creates a new site, so a Zap that fires again makes another one. You must choose a site type: Live is a billable production site, while Staging and Sandbox are free. There's no default, so you can't create a billable site by accident. If your plan has no room for another site of that type, Pressable declines the step and explains why. The site is still provisioning when this step succeeds. Pressable usually emails the account owner when it's done. Setting a WordPress admin email below turns that email off, and so can your account's email settings.

Permanently deletes a Pressable site, including its domain records, collaborators, and backups. You can't undo this from your account. To confirm, you must enter the site's internal name. A successful step means Pressable accepted the deletion, not that it's finished. Use the Site Deleted trigger to confirm. Testing this step in the Zap editor deletes the site, so skip the test unless you really want the site deleted.

Purges a site's edge cache so the next visitor gets fresh content. The step fails if edge cache is disabled for the site. A successful step means Pressable accepted the request, not that every edge location has cleared its copy. Purging twice does no harm.

Turns the edge cache on or off for a Pressable site. You choose the state you want instead of toggling it, so running the step twice has the same result. The change is applied before the step finishes.

Turns maintenance mode on or off for a Pressable site. While it's on, visitors see a maintenance page and you can still use WP Admin. You choose the state you want instead of toggling it, so running the step twice has the same result. The change takes a few moments after the step succeeds, so use Find Site if you need to confirm it.

Enables or disables the WordPress MCP Adapter plugin on a Pressable site, which AI assistants use to reach the site over MCP. Enabling it does not connect an assistant by itself. You choose the state you want instead of toggling it, so running the step twice has the same result. Success means Pressable accepted the request — the plugin change is applied in the background a few moments later.

Updates one or more plugins already installed on a site. Add each plugin as a row in this one step, up to 50. Don't add this action several times for the same site, because each copy waits for the one before it to finish. Plugins that aren't installed won't be installed; their updates fail. Plugins Pressable manages for the platform are skipped without any alert. The update is queued and runs a few moments later, so a successful step means Pressable accepted the request, not that the plugins were updated. To find out about failures, use the Plugin Update Failed trigger, but keep in mind that no alert doesn't prove an update succeeded.

Activates one or more plugins that are already installed on a site, for example after they were deactivated. Add each plugin as a row in this one step, up to 50. A plugin that isn't installed is skipped silently — this step won't install it, and nothing reports it. The activation is queued and runs a few moments later, so a successful step means Pressable accepted the request, not that the plugins were activated. This action has no companion trigger, so if an activation fails later your Zap won't hear about it. Check the plugin on the site if it matters.

Clears a site's object cache. The flush is queued and runs a few moments later, so a successful step means the request was accepted, not that the cache is clear yet. This doesn't purge the CDN.

Requests an on-demand database or filesystem backup for a site. The backup is queued and finishes a few minutes later, so a successful step means Pressable accepted the request, not that the backup exists yet. To act on a finished backup, use the On-Demand Backup Created trigger.

Creates a WordPress user with the role you choose on a Pressable site. WordPress emails the new user a link to set their own password, so no password is sent to Zapier or stored in your Zap history. The email uses WordPress's built-in mail, not an SMTP plugin. If it doesn't arrive, send a password reset from the site's Users screen. Running the step again with the same email fails with "This user already exists" instead of creating a second account. If the step times out, the user may still have been created, so check the site before trying again.

Installs and activates one or more WordPress plugins on a site. Add each plugin as a row in this one step, up to 50. Don't add this action several times for the same site, because each copy waits for the one before it to finish. Plugins are always activated after installing. The install is queued and runs a few moments later, so a successful step means Pressable accepted the request, not that the plugins are installed yet.

Puts a Pressable site behind a username and password prompt, or takes it back out. Visitors sign in with a WordPress username and password for the site. Useful for keeping a staging or pre-launch site private; sandbox sites are not supported. You choose the state you want instead of toggling it, so re-running the step never reverses it. Success means Pressable accepted the request — the change is applied in the background a few moments later. If another Basic Authentication change is still being applied to the site, the step fails with "already in progress" and changes nothing; run it again once that change has finished.

Turns the lightweight 404 response on or off for a Pressable site. When it is on, requests for missing static files (images, CSS, JavaScript, fonts and similar) get a small plain 404 from the web server instead of loading WordPress, which saves resources on sites hit by scanners. Pages your site serves, and missing pages, are unaffected either way. You choose the state you want instead of toggling it, so running the step twice has the same result. The change is applied before the step finishes.

Sets which of a site's domains is primary, meaning the address Pressable serves the site under, or resets it to the staging URL. A successful step means Pressable accepted the change. It takes effect a few seconds later, and DNS or SSL may not be ready yet. If a domain is still being set up, for example right after you add it, Zapier will retry the step later.

Adds up to 50 tags to a site in one step. Tags are shared across all sites on your account. New tags are saved in lowercase and can only contain unaccented letters, numbers, spaces, and the characters - . ( ) &. Adding a tag the site already has won't duplicate it, but each successful run is still recorded in the site's activity log. New tags get a color automatically, which you can change in the Pressable dashboard. Tagging requires the site owner's Manage Tags permission, which is separate from edit access, so a collaborator who can edit a site might not be able to tag it.

Finds a site on your Pressable account by name, domain, or another attribute.