Pressable and Salesflare

How to connect Pressable

About Pressable

Pressable is a managed WordPress hosting platform. Create and manage sites and webhooks, and trigger workflows from hosting events.

Pressable operations on Zapier

Triggers (15)

Start a workflow when this happens

  • Data Transfer Failed — Triggers when a Data Transfer between two of your Pressable sites fails. A Data Transfer copies files, the database, or both from one site to another. Migrations from other hosts don't trigger this. Details explains the failure and often includes how to fix it. Failure Code is a stable reason you can filter on, and Failure Summary explains it in a sentence. Both are empty when Pressable did not classify the failure. Some failures aren't reported. Canceling a transfer may send nothing, or a failure about whatever the cancellation interrupted. Nothing is sent if the destination site was deleted first. In those cases, check the dashboard for failed transfers. If the source site has been deleted, only its ID is included.
  • Data Transfer Succeeded — Triggers when a Data Transfer between two of your Pressable sites succeeds. A Data Transfer copies files, the database, or both from one site to another. Migrations from other hosts don't trigger this. Site names and URLs are current, and if the source site has been deleted, only its ID is included. There's no timestamp field because Pressable doesn't send a completion time.
  • Edge Cache Purged — Triggers when a site's edge cache is purged from the dashboard, the API, a Zap, or by Pressable support. It also fires for some automatic purges: security plugin and theme updates, PHP version updates, site conversions, multisite changes, hacked-site cleanup, and bulk cache clears (one event per site). It doesn't fire for purges during a deploy, repository sync, restore, site sync, scheduled plugin update, plugin or mu-plugin install, or maintenance-mode change.
  • Git Deploy Failed — Triggers when a Git deployment to a site fails. Details gives the reason, such as "Could not clone repo". Deploys interrupted by a connection or timeout error don't send this event, so it won't catch every failure.
  • Git Deploy Succeeded — Triggers when a Git deployment to a site succeeds. Requires the GitHub integration on the site. Commit SHA and Pushed By are filled in for deploys started by a GitHub push and empty for deploys started through the Pressable API. Details is always empty, since Pressable only records a message when a deploy fails.
Show 10 more triggers
  • Hacked Site Detected — Triggers when Pressable marks one of your sites as hacked and disables it. Only Pressable Support can mark it safe again. Still Flagged shows whether the site is still marked hacked when the Zap runs.
  • New Performance Report — Triggers when a performance report is ready. It fires for every report, not just poor scores, including the monthly report for each live site, reports you request, and reports taken around a scheduled plugin update. To act on a threshold, add a Zapier filter on the score fields. Scores are sometimes blank when Pressable can't confirm they match the report, so add an "exists" condition before any threshold.
  • New Site Created — Triggers when a new site finishes provisioning. State shows the site as it is when the Zap runs, not when it was created.
  • On-Demand Backup Created — Triggers when an on-demand backup finishes and is stored. It also fires for backups Pressable takes automatically, such as before a site transfer. Use Customer Requested to tell them apart. Failed backups don't trigger anything.
  • PHP Version Changed — Triggers when a site's PHP version is changed from the dashboard, the API, or by Pressable support. Previous PHP Version is blank for now, because Pressable doesn't send it yet. It doesn't fire for automatic rollbacks of failed upgrades, some bulk changes across many sites, or versions changed outside Pressable.
  • Plugin Update Failed — Triggers when any plugin update fails, whether it was started from the dashboard, the API, the Update Plugins action, or a security alert. The event doesn't say which. It only reports failures, so no event doesn't mean success. The same failure can arrive more than once. Error text isn't included because it can contain file paths or license keys. Requested Version is the version asked for. "latest" means no specific version was requested, not what was installed. The site's name and URL are current.
  • Primary Domain Set — Triggers when a site's primary domain is set from the dashboard, the API, or automatically when a domain is added to a site without one. It also fires when the site is reset to its staging URL (Is Staging URL is true). It fires when the primary domain is removed and another domain takes over, and when a staging or sandbox site gets a custom staging domain as primary (Staging Site is true). One change can send several events, and a new domain can arrive twice with different Domain IDs. DNS and SSL may not be ready yet. It doesn't fire when a site is deleted or for changes made outside Pressable.
  • Site Deleted — Triggers when a site is deleted. The site can't be looked up afterward, so map any fields you need from this step.
  • Site Restore Failed — Triggers when a site restore fails, whether it was started from the dashboard, the API, or by Pressable support. The site's name and URL are current, not from the time of the restore. Failure Code is a stable reason you can filter on, and Failure Summary explains it in a sentence. Both are empty when Pressable did not classify the failure.
  • Site Restored — Triggers when a site restore succeeds, whether it was started from the dashboard, the API, or by Pressable support. The site's name and URL are current, not from the time of the restore.

Actions (18)

Things Salesflare can make it do

  • Activate Plugins — 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.
  • Add Domain — Adds a domain to a site. Adding a bare domain like client.com also adds www.client.com, while a subdomain like shop.client.com adds only itself. If the site has no primary domain, the first domain you add becomes primary. DNS and SSL setup continues for a few minutes after the step succeeds. If the step times out, check the site's domains before trying again.
  • Clear Object Cache — 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.
  • Clone Site — 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.
  • Create On-Demand Backup — 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.
Show 13 more actions
  • Create Site — 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.
  • Create WordPress User — 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.
  • Delete Site — 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.
  • Install Plugins — 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.
  • Purge Edge Cache — 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.
  • Set Basic Authentication — 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.
  • Set Edge Cache — 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.
  • Set Lightweight 404 — 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.
  • Set Maintenance Mode — 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.
  • Set Primary Domain — 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.
  • Set WordPress MCP Plugin — 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.
  • Tag Site — 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.
  • Update Plugins — 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.

Searches (1)

Look up existing records

  • Find Site — Finds a site on your Pressable account by name, domain, or another attribute.

Similar apps

Not using Salesflare yet?

Salesflare is a CRM for small and medium-sized B2B businesses — it fills itself in automatically so your team actually keeps it up to date.

Try it for free