Integrations

Integrations connect NTRVSTA with external systems and automation workflows. Depending on your role and workspace, you may see:

• Notifications
• ATS integrations
• API keys
• Webhooks
• SSO integrations for enterprise setups

At a glance

Connect NTRVSTA to the systems your team already uses

Start with notifications, then add ATS, API, webhook, or SSO integrations as your workflow needs them. Each integration should have a clear owner and a clear reason to exist.

Notifications

Notifications control where completed interviews and flagged results are sent. In NTRVSTA, these are configured as email-based channel notifications:

• Email notifications
• Slack workspace integration
• Microsoft Teams integration

Slack and Teams setups use channel email addresses, so this section is mainly about deciding where your team wants to receive operational updates.

ATS Integrations

Connect NTRVSTA with supported ATS providers for candidate sourcing and interview workflow handoff. Configure provider credentials and related setup from the integrations area.

Depending on the ATS, setup can also include the stage or status values that should be used when an interview is scheduled or completed.

If you need a custom integration not listed here, contact support.

API Keys

Manage external integration API keys. These keys authenticate calls to the public REST API and can be created, copied once, and revoked.

Use separate keys for different environments or partners when possible so access is easier to manage and revoke later.

Webhooks

Configure webhook endpoints for event-driven integrations. Manage the destination URL, signing secret, and delivery behavior for outbound result events.

The current documented event is result.completed, which lets your systems react as soon as an interview report is ready.

Recent delivery health is also visible in this section, which makes it easier to spot failed webhook attempts without leaving the app.

SSO Integrations

Enterprise workspaces may also expose SSO integrations so team members can sign in through an identity provider such as Okta.

Recommended Setup Order

1. Turn on the notifications your team actually monitors
2. Add ATS integrations if your workflow depends on them
3. Create API keys for external systems
4. Configure webhooks for automated downstream processing
5. Add SSO when your organization is ready for managed sign-in