# Netskope integrations: event exports

> Export alert events, create an iterator and submit a UCI impact in Netskope.

**Canonical page:** https://tray.ai/connectors/netskope-integrations/
**Categories:** Security and compliance
**Connects through:** HTTP Connector

## Overview

Netskope is a cloud security platform that inspects web, SaaS and private app traffic, enforcing data protection and threat policies and logging alerts and events. Tray.ai connects to Netskope through the HTTP Connector, so your workflows can call the Netskope API alongside the rest of your stack.

## Use cases

### Event exports

Read event exports in Netskope from any Tray.ai workflow. The Netskope API covers calls such as export alert events and fetch the next page.

- Export alert events
- Fetch the next page
- Resend the last page

### Client status iterators

Read, create, and delete client status iterators in Netskope from any Tray.ai workflow. The Netskope API covers calls such as create an iterator and check iterator status.

- Create an iterator
- Check iterator status
- Fetch iterator events

### Anomalies

Read and create anomalies in Netskope from any Tray.ai workflow. The Netskope API covers calls such as submit a UCI impact and get an anomaly.

- Submit a UCI impact
- Get an anomaly
- Search anomalies

## Challenges Tray.ai solves

### Keeping Netskope credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Netskope credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Netskope API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Netskope API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Netskope?

Yes. Tray.ai connects to Netskope through the HTTP Connector, which calls the Netskope API directly. Any call the Netskope API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Netskope?

The Netskope API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Netskope connector?

Netskope runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Netskope connector from the Netskope API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/