Product guides

Integrations in the Console

Suggest Edits

Code Defender has a variety of integrations to work with your current tech stack and maximize your team’s efficiency. You can access integrations from Code Defender’s Product Settings > Integrations > Integration Settings.

Slack

The Slack integration lets Code Defender send automated notifications and messages to Slack channels you specify.

  1. On the Slack integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Slack integration and how it will appear in the HUMAN console.
    • Slack webhook URL: The webhook URL for your Slack integration. Must be in the form https://hooks.slack.com.
    • Slack channel: The Slack channel Code Defender should send messages to. Must be in the form #slack-channel.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Email

The Email integration lets Code Defender send automated emails when an alert is triggered.

  1. On the Email integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Email integration and how it will appear in the HUMAN console.
    • Email: The email addresses Code Defender should send emails to. Press Enter after each email to add multiple addresses.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Jira

The Jira integration lets you create Jira issues from Code Defender alerts.

  1. On the Jira integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your Email integration and how it will appear in the HUMAN console.
    • Jira webhook URL: The webhook URL for your Jira integration. Must be in the form https://****.atlassian.net.
    • Jira project ID: The ID for the Jira project Code Defender should create issues in.
    • API token: Your Jira API token.
    • Default reporter email: The email address for the default reporter for issues.
    • Desired issue type: The type of task Code Defender should create for issues by default. The selected task type must also exist in the specified Jira project. This field is optional.
    • Add event risk level priority: Choose whether to assign the ticket a priority level. If you choose to add one, Code Defender will assign the ticket priority based on the incident’s risk level. For example, high-risk incidents will create a high-priority issue. The priority field must exist in the issue in Jira for this feature to sync properly. This field is optional.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

PagerDuty Events

The PaterDuty Events integration lets you send events from Code Defender to create incidents.

📘

Note

The PagerDuty Events integration is a separate integration from the PagerDuty integration. To integrate with the latter, you must contact our team instead. For more, see our help article.

  1. On the PagerDuty Events integration, select Add integration.
  2. Complete the following fields:
    • Integration name: The name of your PagerDuty Event integration and how it will appear in the HUMAN console.
    • Webhook URL: The webhook URL for the PagerDuty Event you are integrating with. Must be in the form https://events.pagerduty.com/v2/enque.
    • API key: Your PagerDuty API authentication key.
  3. Select Test to confirm your integration is working.
  4. Once your test is successful, select Save.

Your integration has been successfully created.

Splunk

The Splunk integration lets you search and visualize data sent from Code Defender.

  1. On the Splunk integration, select Add Integration.
  2. Complete the following fields:
    • Integration name: The name of your Splunk integration and how it will appear in the HUMAN console.
    • Splunk webhook URL: The webhook URL for your Splunk integration. Must be in the form https://<customer-identifier>.splunkcloud.com/services/collector.
    • API token: Your Splunk API token.
    • Custom Splunk index: The Splunk index that HUMAN should send information to. This field is optional.
  3. Select Test connection to confirm your integration is working.
  4. Once your test is successful, select Save changes.

Your integration has been successfully created.

Updated 12 days ago