LogoLogo
WebsitePricingBlog
  • Debricked Documentation
  • Overview
    • Getting started
      • Create a OpenText Core SCA account
      • Running OpenText Core SCA
    • Help
      • Frequently asked questions (FAQ)
      • Upgrade your account
      • Get help in OpenText Core SCA tool
    • Language support
      • C# - Nuget, Paket
      • CycloneDX SBOM
      • Go - Go Modules, Go Dep, Bazel
      • Java & Kotlin - Gradle, Maven, Bazel
      • JavaScript - NPM, Yarn, Bower
      • Objective-C - CocoaPods
      • PHP - Composer
      • Python - Pip, Pipenv
      • Ruby - RubyGems
      • Rust - Cargo
      • Swift - CocoaPods
      • Linux package managers
      • Scala - SBT
    • Security overview
  • Product
    • Vulnerability management
      • Security terms
      • Data sources
      • See your data
      • Pull Requests (PR)
        • Enable Pull Request support
        • Solve vulnerabilities using Pull Requests (PR)
        • Solve vulnerabilities using Pull Requests (PR) via API
      • Set a review status
        • Snooze or pause a review status
      • Reachability Analysis
        • Set up Reachability Analysis for Java
        • Set up Reachability Analysis for Go
      • Solve vulnerabilities manually with root fixes
    • License risk management
      • Licence families
      • License risks
      • Set up a use case
        • Set up a use case using API
      • Proxy non-standard license identifiers
    • Project health
      • Contributors
      • Popularity
      • Security
    • Open source select
      • Search projects
      • Compare projects
      • View more details
      • Start left policies
      • OpenText Core SCA Select Browser Extension
      • End of Life (EOL)
    • Automation
      • Create an automation rule
      • Edit an automation rule
      • Default automation rules
      • Set up webhooks
      • Policies
      • Monitoring
    • Exporting or SBOM
      • Overview
      • License export
      • Vulnerability export
      • SBOM export
        • CycloneDX SBOM export
        • SPDX SBOM export
    • Administration
      • Generate access token
      • Account
        • Change your password
        • Delete your account
        • Delete company account
      • Billing
        • Manage contributing developers
        • Manage billing frequency
        • Manage payment methods
        • Access invoices
        • Manage your subscription
      • Settings
        • Enable and disable snoozing vulnerabilities
        • Supported language for Debricked tool
        • View logged events
        • Two-Factor Authentication (2FA)
      • Users
        • User roles (freemium and premium)
        • Role-Based Access Control (Enterprise)
        • Manage users
          • Add a new user
      • Repositories
        • Default Branch
        • Repository groups
        • Manually upload a dependency file
        • Manage your commits
  • Tools & Integrations
    • Command Line Interface (CLI)
      • Debricked CLI
        • High performance scans
        • File fingerprinting
      • Legacy CLI
    • CI/CD integrations
      • GitHub
      • CircleCI
      • BuildKite
      • GitLab
      • Bitbucket
      • Azure DevOps
      • Argo workflows
      • Travis CI
      • Jenkins
      • Bamboo
      • TeamCity
    • Fortify on Demand (FoD)
    • Fortify Software Security Center (SSC)
    • Debricked APIs
      • Open source select API
    • Integrated Development Environments (IDEs)
    • Single Sign-On (SSO)
      • Single Sign-On (SSO) through Okta
      • Single Sign-On (SSO) through Microsoft Entra ID
      • Single Sign-On (SSO) through JumpCloud OIDC
      • Single Sign-On (SSO) through GitHub
  • Tips & Tricks
    • Debricked CLI migration guide
    • Workarounds
      • Scanning Conan (C++) projects
      • Scanning a repository with different services
      • Scanning Docker images
      • Automations: Do not fail on found CVE lacking a fix
Powered by GitBook
LogoLogo

Company

  • Pricing
  • Blog

Support

  • Privacy Policy
  • Terms & Conditions
  • Service Status

Resources

  • Vulnerability DB
  • Open Source Select

© 2018-2024 | Open Text

On this page
  • Send a sample request
  • Verification secret
  • Set up a webhook with slack through Zapier
  • Set up notifications in slack using webhook

Was this helpful?

Export as PDF
  1. Product
  2. Automation

Set up webhooks

Learn how to set up and configure a webhook.

In order to send a webhook request when an automation rule is triggered, add a "trigger webhook" action to the rule and enter the URL for the webhook in the URL field. When the rule is triggered, a POST request will be sent to the given URL with JSON-encoded data about the event.

The JSON will contain the following keys:

Key
Type
Description

repository

string

Name of the repository which was scanned

branch

string

Name of the branch which was scanned

commit

string

Name of the commit which was scanned

commitLink

string

Link to a page debricked.com, where scan results for this commit are available

ruleId

integer

Unique identifier for the rule that was triggered

ruleLink

string

Link to a page in debricked.com, where the triggered rule can be viewed or edited

triggeredFor

array

Array of objects, where each element describes a combination of a vulnerability and a dependency which caused the rule to trigger

Each element of triggeredFor will contain the following keys:

Key
Type
Description

dependency

string

Name of the dependency which caused the rule to trigger

dependencyLicenses

array

Array of licenses affecting the dependency, each encoded as a string using the same name as shown in the license view

dependencyLink

string

Link to the dependency on debricked.com

cve

object / null

Information about the vulnerability which caused the rule to trigger, or null if the rule doesn't have any conditions related to vulnerabilities

cve.name

string

Name of the vulnerability that caused the rule to trigger

cve.link

strint

Link to the vulnerability on debricked.com

cve.cvss2

number / null

CVSS2 score for the vulnerability, or null if not available

cve.cvss3

number / null

CVSS3 score for the vulnerability, or null if not available

Send a sample request

A sample webhook request can be sent to the specified URL by clicking Send sample request. The triggeredFor array will be populated using up to three vulnerabilities that were found the last time this repository was scanned. Note that these vulnerabilities may not necessarily fulfill the conditions specified in the rule.

Verification secret

To ensure that a webhook request was sent by Debricked, a key can be specified in the verification secret field. When a verification secret is specified, webhook requests made by this rule will include the header X-Debricked-Signature, containing an SHA256-HMAC signature generated using the webhook payload and the verification secret.

Set up a webhook with slack through Zapier

You can use the automation engine to send notifications to Slack, with the help of middleware, e.g. Zapier. Keep in mind that this is currently only possible using the premium version of Zapier.

To create a webhook URL:

  1. Click +Create Zap.

  2. Search for and select Webhooks by Zapier.

  3. Go to the Event drop-down, select Catch Hook and click Continue.

  4. Copy the Webhook URLI.

  5. Click Continue and then Test trigger.

  6. Once you have the URL, open the Debricked tool and go to Automations on the left-side menu.

  7. You can either create a new rule or edit an existing one in the Then statement. Once done, add the trigger webhook action.

  8. Paste the Webhook URL copied from Zapier into the field.

  9. If needed, click Send sample request to test if everything works correctly.

  10. Click Generate rule and Save.

Set up notifications in slack using webhook

To manage your notifications in Slack:

  1. Click Action and select Slack.

  2. Go to the Event drop-down and select the desired action. For example, Send Channel Message.

  3. Click Choose account and follow the instructions on the page to connect your Slack account to Zapier.

  4. Click Set up action and select the data that you want to send.

  5. Click Message text and select the information to be included in the message.

  6. Click Test action.

  7. Click Publish Zap.

Now you are ready to receive Slack notifications from Debricked!

Last updated 3 months ago

Was this helpful?

Open .

Open .

Zapier
Zapier