Integrations

Setting Up Integrations

The generic flow for connecting any integration: select a provider, configure credentials, choose events, and test.

General Setup Flow

All APVISO integrations follow the same setup pattern. The specifics vary by provider, but the overall flow is consistent.

Step 1 — Select Provider

Navigate to Settings → Integrations → Add Integration. Browse or search the list of available providers. Click the one you want to set up.

Step 2 — Authenticate

Depending on the provider, authentication works in one of several ways:

  • OAuth (Jira, Slack, GitHub, GitLab) — click Connect and authorize APVISO in the provider's consent screen. Tokens are stored encrypted.
  • API key (PagerDuty, Opsgenie, Datadog) — paste your API key or token from the provider's settings.
  • Webhook URL (Slack incoming webhook, Discord, custom) — paste the webhook endpoint URL.

Step 3 — Configure

After authentication, configure provider-specific settings:

  • Jira — select the project, issue type, and field mappings (severity → priority, etc.).
  • Slack — choose the channel to post to.
  • GitHub Issues — select the repository and label configuration.
  • PagerDuty — select the service and severity-to-urgency mapping.

Step 4 — Choose Events

Select which event types trigger this integration. For example, you might configure Jira to create issues only on finding.created events, while Slack receives all events.

Step 5 — Test

Click Send Test Event to verify the integration is working. APVISO sends a sample payload and reports whether delivery succeeded.

Step 6 — Save and Enable

Click Save. The integration is now active and will fire on the selected events.

Managing Integrations

From the integrations list you can:

  • Edit — update configuration, credentials, or event selection.
  • Disable — temporarily stop the integration without deleting it.
  • Delete — permanently remove the integration.

Delivery Logs

Every integration includes a delivery log showing recent event deliveries, their HTTP status, response time, and any error messages. Use this to troubleshoot failed deliveries.

Retry Behavior

Failed deliveries are retried up to 3 times with exponential backoff (1 minute, 5 minutes, 30 minutes). If all retries fail, the delivery is marked as failed and appears in the delivery log with error details.

Security

All credentials and tokens are encrypted at rest using AES-256. OAuth tokens are refreshed automatically. API keys and webhook URLs are never exposed in the UI after initial entry.

Back to Knowledge Base