Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet.

Skip to content

Creating a trigger

New triggers can be created on the Developer and Business plan only.

You can create a trigger by clicking on + Create Trigger on the Alerts page in Patchstack App or by navigating here: https://app.patchstack.com/alerts/create.

  1. Give your trigger a name by typing it into Trigger Title field.
  2. Select the condition of when the alert is triggered from the dropdown
  3. The dropdown includes the following conditions:
    • Component Event
      • Outdated - sends an alert, when a component on your site is outdated
      • Vulnerable - sends an alert, when a component on your site is vulnerable
    • WordPress Activity Event
      • User Logged In - sends an alert, when someone logs in to WordPress
      • User Registered - sends an alert, when a new account is created in WordPress
      • Post Deleted - sends an alert, when a post is deleted from WordPress
      • Post Trashed - sends an alert, when a post is sent to the trash in WordPress
      • Attachment Uploaded - sends an alert, when an attachment is uploaded to WordPress
      • Plugin Installed - sends an alert, when a new plugin gets installed on WordPress
      • Plugin Deactivated - sends an alert, when a plugin is deactivated on WordPress
      • Plugin Activated - sends an alert, when a plugin is activated on WordPress
    • Firewall Logs Event
      • Match IP - sends an alert, when your site gets visited from a certain URL
      • Match URL - sends an alert, when a certain URL gets visited
      • Match Payload - sends an alert, when a certain payload is submitted
  4. Depending on a condition, you may be asked to set additional parameters to the conditions. For example by choosing "Match IP", you will have to choose, whether the status has to equal or be bigger than the code you type.

    You will see the conclusion of your built rule before saving it (see the image below).

  5. The next step is to choose whether you would like to get notified to your email, Slack channel, or both.
  6. After having set your rules, click on + Create Trigger.
  7. You will be then directed back to the Alerts page where you can see your new trigger on the right side of the page.
1