Automate and Integrate your WebOps Workflow with Quicksilver

Learn how to use Quicksilver to automate your WebOps workflow.

Discuss in our Forum Discuss in Slack

Quicksilver hooks into platform workflows to automate your Pantheon WebOps workflow. This allows the platform to run selected scripts automatically every hour, or when a team member triggers the corresponding workflow. There is a growing set of example scripts that you can contribute to. You can also find examples to enable functionality like chat-ops, database sanitization, deployment logging, and automated testing operations with a CI server.

Quicksilver Cloud Hooks Training

Set up existing scripts and write your own with help from our experts. Pantheon delivers on-demand training to help development teams master our platform and improve their internal WebOps.

For example, committing a pantheon.yml file with the following contents to the root of your site's code repository with the script adapted from slack_notification will post to Slack every time you deploy:

api_version: 1

      - type: webphp
        description: Post deployment notification to Slack
        script: private/scripts/slack_deploy_notification.php

Add the following after the previous snippet to have it automatically log the deployment to New Relic:

      - type: webphp
        description: Log to New Relic
        script: private/scripts/new_relic_deploy.php

WebOps Workflow and Stage

Specify the workflows you want to hook into (e.g., deploy or sync_code) the workflow stage (before or after) and the location of the script relative to the root of your site's docroot.

Quicksilver and the Deploy Hook

Before using a Quicksilver hook for a deploy workflow, deploy your pantheon.yml file into an environment.

Quicksilver scripts that trigger on the deploy hook operate on the state of the code at the time of the deploy, not the state of the code after the deploy. This means that new or updated code is not available until the deployment finishes even though the deploy hook is triggered at the start of the deploy.

Script Type and Location

Quicksilver currently supports webphp scripting, which runs a PHP script through the same runtime environment as the website. PHP scripts are subject to the same limits as any code on the platform, such as timeouts. PHP scripts cannot be batched, and run continuously and sequentially. Each command executes after the previous command has finished or timed out.

We recommend setting the web_docroot to true to create a dedicated directory in the docroot (for example, private/scripts). This tracks files by instructing Quicksilver to look for the files inside the web folder. If your site uses this nested docroot setting, the scripts directory must be located in the web subdirectory of your site's code repository (for example, web/private/scripts).


If your site uses a nested docroot, the script paths in your pantheon.yml file should not include the web/ path prefix. Scripts in your pantheon.yml file should match the following path examples: private/scripts/new_relic_deploy.php or private/scripts/slack_deploy_notification.php

Composer Script Installs

You can use Terminus to install Quicksilver Composer scripts if you have a Composer-managed site. The sections below provide links to Pantheon-maintained repositories with install scripts.


Your script may require tokens, passwords, or other information that should be protected. These values should be stored securely. You can do this with a third-party key management service like Lockr.

You can also use your site's private files path to store values securely. When storing keys for Quicksilver scripts in the private files path, be aware that the Site Dashboard function to copy files from one environment to another will also overwrite the private files path.

  1. Install the Terminus Secrets Plugin to manage secret data in JSON files in your site's private files path.

    This will allow you to write and remove key values. The code example below shows you how to write a value to a key:

    terminus secrets:set site.env key value

Clear Cloudflare Cache

Use the Pantheon Cloudflare Cache repository to clear your Cloudflare cache.


Always clear your CDN cache using the after timing option to avoid requests re-caching stale content. Caches should generally be cleared "bottom up".

Debugging with Quicksilver

Use the Pantheon Quicksilver Debugging repository to explore Quicksilver as a workflow improvement tool.

Drush CMI

The Pantheon Drush CMI repository provides steps on how to integrate Drush commands into your Quicksilver operations. This allows you to import configuration changes from .yml files.

Drush Revert Features

The Pantheon Drush Revert Features repository provides information on using Drush to commands to revert specific features.

Enable Development Modules

The Pantheon Enable Development Module repository provides steps on how to use Drush within a Quicksilver script.

Generate Development Content

Use the Pantheon Generate Development Content repository to integrate Drush devel generate commands into your Quicksilver operations. This allows you to generate development content on each database clone operation.

Import WP-CFM Configuration Settings into a Cloned Database

Use the Pantheon WP-CFM Import repository to automatically import WP-CFM configuration settings into a cloned database. This is useful for development environments that have slightly different settings than the production environment.


WP-CFM should only be used to write changes to code in Dev and Multidev environments, where the code base is writable. Cloning databases between environments before saving WP-CFM bundles can result in loss of data.

New Relic Custom Apdex T Values Multidev Environments

Use the Pantheon New Relic Apdex T Values repository to set custom T values for Multidev environments. Each environment will use the default values of 0.5 and 7 for your server and browser, respectively, if you don't set a custom value.

New Relic Deploy Markers

Use the Pantheon New Relic Deploy Markers repository to automatically log changes to your site into New Relic's Deployments page. This can be useful for keeping track of performance improvements.

Search and Replace URLs on WordPress Sites

Use the Pantheon Search and Replace URLs on WordPress Sites repository to automatically find and replace URLs in the database of a WordPress website. This is helpful for sites that have multiple domains in an environment.

Slack Integration

Use the Pantheon Slack Integration repository to integrate Slack notifications from your Pantheon project using Quicksilver. This integration overview also provides information on how to manage API keys outside of your site repository.

URL Checker

Use the Pantheon URL Checker repository to check specific URLs after a live deployment. This script also notifies you of failures by email.


Use the Pantheon Quicksilver Webhooks repository to post workflow data to an external URL for a generic Webhook implementation.


You can hook into the following workflows:

WorkflowDescriptionLocation of webphp runtimeNotes
autopilot_vrtAutopilot Visual Regression test"Autopilot" Multidevafter stage valid, before stage invalid
clear_cacheClear CMS and Edge Cache
clone_databaseClone database between environmentstarget (to_env)
create_cloud_development_environmentCreate Multidev environmentMultidevafter stage valid, before stage invalid
deployDeploy code to Test or Livetarget
deploy_productCreate siteDevafter stage valid, before stage invalid
sync_codeUse the command git push command to change the code; commit via the Pantheon Dashboard, upstream update, Multidev merge, or automated workflowsDev or Multidev


For sites using Integrated Composer, the sync_code hook runs after the build finishes and the artifacts have been completely deployed to the application server.


Variables are made available through the $_POST global variable, and the $_ENV and $_SERVER objects. These variables include the following:

Variable NameDescriptionHooks AvailableNotes
trace_idThe unique ID of the workflowAll
site_idUUID of the site instanceAll
environmentEnvironment name that the workflow is running onAllMatches the PANTHEON_ENVIRONMENT environment variable
stagebefore or after indicator for when the workflow is runningAll
qs_descriptionDescription of the workflow as defined in pantheon.ymlAll
wf_typeID of the workflow hook that is runningAll
wf_descriptionLabel of the workflow hook that is runningAll
user_idUUID of the user account that initiated the taskAllIf the task is initiated by Pantheon, user_id is None
user_firstnameFirst name of the user account that initiated the taskAllIf the task is initiated by Pantheon, user_firstname is Pantheon
user_lastnameLast name of the user account that initiated the taskAllIf the task is initiated by Pantheon, user_lastname is Pantheon
user_fullnameUUID of the user account that initiated the taskAllIf the task is initiated by Pantheon, user_fullname is Pantheon
user_emailEmail of the user account that initiated the taskAllIf the task is initiated by Pantheon, user_email is
user_roleUUID of the user that initiated the taskAll
to_environmentTarget environment where the database is being cloned toclone_database
from_environmentSource environment where the database is being cloned fromclone_database
deploy_messageDeploy message provided as part of a test of live deploymentdeployThis is only available if a deploy message is provided
vrt_statusResult of the visual regression testautopilot_vrt
vrt_result_urlPage URL associated with an Autopilot VRT resultautopilot_vrtAutopilot is only available in the new Pantheon Dashboard
updates_infoList of the plugins/modules/themes that were updated prior to the VRTautopilot_vrtReturns JSON data structure

For examples on how to use these variables, see the Quicksilver Examples repository.

Debugging via Terminus

Use the following Terminus commands for debugging Quicksilver.

Stream New Workflows to the Console

Follow the WebOps activity of your site with terminus workflow:watch <site>.

Explore Previous Workflows

List and show previous workflows and their corresponding Quicksilver operations with the following commands:

  • terminus workflow:list <site>
  • terminus workflow:info:logs <site> --id=<workflow>
  • terminus workflow:info:operations <site> --id=<workflow>
  • terminus workflow:info:status <site> --id=<workflow>


MultiDev Creation Hook Does Not Run When Expected

Quicksilver hooks for the create_cloud_development_environment workflow will not be detected when creating a Multidev environment if the pantheon.yml file does not exist on the Dev environment. As a workaround, commit the pantheon.yml file on Dev before creating a Multidev environment.

Deploying Configuration Changes or Quicksilver Hooks to Multidev

If a pantheon.yml file does not exist on the Dev environment, configuration changes will not be detected when creating a Multidev environment. As a workaround, make some modification the pantheon.yml file and re-commit to the Multidev environment. You will then receive a notice indicating configuration changes have been detected and applied to the Multidev environment:

remote: Changes to `pantheon.yml` detected.
remote: Successfully applied `pantheon.yml` to the 'new-feature' environment.

Autopilot VRT Hook Does Not Run When Expected

For some Autopilot users, Quicksilver hooks are not detected due to timing issues with Multidev creation. If your Quicksilver autopilot_vrt scripts are not running, first make sure that your scripts are defined in the Dev environment, and then try deleting your Autopilot Multidev from the dashboard. Be sure to also delete the Autopilot branch, and then create the Autopilot Multidev again in the Dashboard. Once you do this, your scripts should start running after the visual regression tests complete.

See Also