Contact Support


Integrating Netsparker Standard with Clubhouse

Clubhouse is a project management platform specifically designed for software development. Clubhouse helps bring teams of all sizes together to build better products, from project planning to project creation.

This topic explains how to configure Netsparker Standard to send a detected vulnerability to Clubhouse.

For further information, see Configuring the User Interface for Custom Send To Actions in Netsparker Standard and Configuring Auto Send To Actions in Netsparker Standard and What Systems Does Netsparker Integrate With?.

Clubhouse Fields

The table lists and describes the Clubhouse fields in the Send To Actions tab.




Click to add an integration.


Click to delete the integration and clear all fields.

Configure Send To

Click to configure the integration using the Settings Wizard instead of doing it manually.

Create Sample Issue

Once all relevant fields have been configured, click to create a sample issue.


This section contains general fields about the Send To Action.

Display Name

This is the name of the configuration that will be shown on menus.


This section contains fields that must be completed.

API Token

The API token.

Project ID

This is the ID of the project to which the issue belongs.

Story Type

This is the issue's story type.

The options are:

  • Feature
  • Chore
  • Bug


This section contains fields with vulnerability details.

Body Template

The template file to be used while rendering issue contents.


The string to be used while formatting vulnerability title


This section contains optional fields.

Epic ID

This is the epic identifier.

State ID

This is the workflow state identifier that the Story is in.

Requester ID

This the member identifier of the person who requested the issue.

Owner IDs

This is a comma-separated list of member identifiers of those who own the issue.

Follower IDs

This is a comma-separated list of member identifiers of those who follow the issue.

Due Days

This is the number of days between the date the issue was created to the date it’s due.


This is a comma-separated list of labels.

How to Integrate Netsparker Standard with Clubhouse

  1. Open Netsparker Standard.
  2. From the Home tab on the ribbon, click Options. The Options dialog is displayed.
  3. Click Send To Actions.

  1. From the Add dropdown, select Clubhouse

The Clubhouse fields are displayed.

  1. In the Mandatory section, complete the connection details:
    • API Token
    • Project ID
    • Story Type
  2. In the Vulnerability section, you can specify the Body Template and Title Format.
Body templates are stored in %userprofile%\Documents\Netsparker\Resources\Send To Templates. If you use your own custom templates, store them in this location.
  1. In the Optional settings you can specify:
    • Epic ID
    • State ID
    • Requester ID
    • Owner IDs
    • Follower IDs
    • Due Days
    • Labels
  2. Click Create Sample Issue to confirm that Netsparker Standard can connect to the configured system and create a sample issue. The Send To Action Test dialog is displayed to show if the sample issue is successfully created.

  1. In the Send To Action dialog, click the Issue number link to open the issue in default browser.

How to Export Reported Vulnerabilities to Projects in Clubhouse

  1. Open Netsparker Standard.
  2. From the ribbon, select the File tab. Local Scans are displayed. Double-click the relevant scan to display its results.
  3. In the Issues panel, right click the vulnerability and select Send To Clubhouse. (Alternatively, click the Send To Clubhousebutton in the Vulnerability tab on the ribbon menu.)

  1. Click the Clubhouse Send to Action is executed for the selected vulnerability link to see the created issue in Clubhouse.

The vulnerability is now automatically exported to Clubhouse. You can view it in the Clubhouse Issues tab.


Highly accurate, fast & easy-to-use Web Application Security Scanner

Get a demo