Shared Features

Integrations

Connect WorkVerge to HRIS, cloud providers, registrars, and Slack so Maya's team syncs employees, discovers servers, and delivers alerts without duplicate data entry.

Real-world scenario

Maya Chen · IT Manager at Bluewave Labs

Maya is rolling out Slack alerts before prod-api-01 maintenance. She connects Slack under Notifications, verifies Google Workspace employee sync, and confirms AWS instances flow into ITAM for Carlos.

Before you begin

  • Org admin access to My Organization → Integrations
  • Vendor admin credentials or OAuth approver

Overview

Integrations are the front door for directory sync, asset discovery, and third-party notifications. Everything starts in My Organization → Integrations, connect once, then each product module consumes the imported data on its own schedules and detail pages.

General setup

  1. 1

    Open My Organization → Integrations

    You will see categories for Employees, Domains, Servers, and Notifications, pick the area you are connecting first.

  2. 2

    Select the integration and click Connect

    Follow the OAuth wizard for Google, Microsoft, Slack, or cloud providers; paste API keys where required.

  3. 3

    Configure sync scope

    Choose full directory import vs. selected groups or tags so you do not pull personal tenants into production.

  4. 4

    Run initial sync and verify records

    Check Employees, domain lists, or server inventory in the target module. Fix mapping errors before enabling schedules.

  5. 5

    Enable ongoing sync where supported

    Turn on scheduled sync for HRIS and cloud discovery so Carlos is not manually reconciling every Monday.

HRIS & directory

  • HRIS sync. Employees, departments, start dates via background workers
  • Google Workspace. Users, groups, calendar
  • Microsoft 365. Users and calendar

Synced employees populate Employees & Teams and DEX folder targeting for Priya's deployments.

Slack for notifications

  1. 1

    Under Integrations → Notifications, connect Slack

    Authorize the WorkVerge app for your workspace. You need Slack admin approval.

  2. 2

    Choose workspace and install scopes

    Grant post-message permissions for alert channels Maya defines.

  3. 3

    Return to notification settings

    Map alert types to #it-alerts, #platform-alerts, and other channels, see Notifications for the full routing table.

Bluewave Labs: Slack install

  • Workspace: WorkVerge-labs.slack.com
  • Installed app: WorkVerge Notifications
  • First test: Post to #it-alerts from a staging domain expiry rule
  • Owner: Maya Chen (channel mapping), Carlos Reyes (uptime alerts)

Integrations vs. notification prefs

Connecting Slack here unlocks delivery. Channel mapping and alert types are configured in Notifications.

Domains & servers

Domain integrations

  • Cloudflare. Sync domains and DNS
  • GoDaddy. Sync domains
  • Namecheap. Sync domains (Bluewave uses Namecheap for workverge.ai)

Server integrations

  • AWS. EC2 instances
  • Hetzner, Digital Ocean, Google Cloud, Azure. Cloud VMs

See Server Integrations for field mapping and discovery schedules Carlos uses after Maya connects AWS.

Zapier & webhooks

Use the Zapier tab under Integrations for webhook-based automations with external tools. Test in staging before pointing at production ticket or asset flows.

Related articles