Testing Integration Instances: Validate Your Connections

Test instances of step integrations upon configuration to ensure proper functionality. Quickly verify that your integration authentication parameters are correctly configured so you can confidently build reliable workflows and streamline the setup process for smoother, more efficient automation.

Once you have set the necessary parameters for your specific integration, validate the connection by clicking the Test Integration button. An HTTP request will be sent to a vendor-specific endpoint to validate the authentication.

The test will verify that the connection is functioning but not verify that the integration permissions were correctly established.

The following table shows which integrations have the testing feature and which HTTP call is used. Currently, only step integrations are testable. Testing OAuth integrations is done automatically when saving.

Step Integration	HTTP call used for test
Okta	`https://{{ .OKTA_DOMAIN }}/api/v1/users?limit=1`
VirusTotal	`{{ .BASE_URL }}/ip_addresses/8.8.8.8`
ServiceNow	`https://{{ .SN_INSTANCE }}.service-now.com/api/now/table/sys_user?sysparm_limit=1`
Cortex XDR	`{{ .CORTEX_XDR_BASE_URL }}/api_keys/validate`
SentinelOne	`https://{{ .S1_MGMT_URL }}//web/api/v2.1/user`
AbuseIPDB	`https://api.abuseipdb.com/api/v2/account`
Splunk Enterprise	`{{ .SPLUNK_URL }}/services/authentication/current-context`
UrlScan	`https://urlscan.io/user/quotas`
AlienVault OTX	`https://otx.alienvault.com/api/v1/pulses/subscribed?page=1`
Qualys	`https://{{ .QUALYS_BASE_URL }}/api/2.0/fo/scan/?action=list`
Defender 365	`https://login.microsoftonline.com/{{ .TENANT_ID }}/oauth2/v2.0/token`
Defender Endpoint	`https://login.microsoftonline.com/{{ .TENANT_ID }}/oauth2/v2.0/token`

Palo Alto Networks Cortex XDR

Britive

Trigger a Workflow with an Integration Trigger: Sync/Async Options

OAuth 2.0

Microsoft 365