# Olostep integrations: scrapes and crawls and maps

> Create a map, create a batch and create a schedule in Olostep, and start a workflow when Olostep sends “Batch completed”.

**Canonical page:** https://tray.ai/connectors/olostep-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Olostep is a web data API that scrapes pages, crawls sites and maps URLs, returning Markdown, HTML, screenshots or structured JSON. Tray.ai connects to Olostep through the HTTP Connector, so your workflows can call the Olostep API alongside the rest of your stack.

## Use cases

### Scrapes

Read and manage scrapes in Olostep from any Tray.ai workflow. The Olostep API covers calls such as scrape a URL and retrieve scraped content.

- Scrape a URL
- Retrieve scraped content

### Crawls and maps

Read and create crawls and maps in Olostep from any Tray.ai workflow. The Olostep API covers calls such as start a crawl and create a map.

- Start a crawl
- Create a map
- Get a map

### Batches

Read and create batches in Olostep from any Tray.ai workflow. The Olostep API covers calls such as create a batch and get batch info.

- Create a batch
- Get batch info
- List batch items

### Schedules

Read, create, and delete schedules in Olostep from any Tray.ai workflow. The Olostep API covers calls such as create a schedule and list schedules.

- Create a schedule
- List schedules
- Delete a schedule

### Files

Read, create, and delete files in Olostep from any Tray.ai workflow. The Olostep API covers calls such as upload a file and list files.

- Upload a file
- List files
- Delete a file

### Olostep events

Start a Tray.ai workflow the moment something happens in Olostep. Olostep sends events such as batch completed and crawl completed to a Tray.ai webhook trigger.

- Batch completed
- Crawl completed

## Challenges Tray.ai solves

### Keeping Olostep 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 Olostep 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 Olostep 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 Olostep 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 Olostep?

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

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

The Olostep API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Olostep connector?

Olostep runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Olostep connector from the Olostep 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/
