Before you start
- An Olostep account with an API key: get one free, no credit card required. Your first 500 credits are included.
- A Relay account: create one at relay.app.
- No coding required: everything in this guide is done through Relay’s visual editor.
Setup
Find Olostep in Relay
Open a workflow in Relay, add a step, and search for Olostep. Select Olostep from the app list.
Choose an action
After selecting Olostep, choose one of the available Olostep actions in the step configuration.
Connect your account
Click Connect account, paste your Olostep API key, and authorize the connection. Relay will save this account for future workflows.
Configure Scrape Website (URL + format)
- URL to Scrape: map from a previous step or enter manually
-
Output Format: choose
Markdown,HTML,JSON, orText
Actions
Scrape Website
Pull content from any URL as Markdown, HTML, JSON, or plain text. Handles JS-rendered pages with optional wait times and country targeting.
Create Map
Get every URL on a site without scraping content. Use it for discovery before a batch job. Returns a
map_id.Map is async. Store the returned
map_id and use a delay/poll pattern in Relay to retrieve results once processing completes.Example workflow: Scheduled competitor page scrape
What it does: On a schedule, this workflow scrapes a competitor page and stores clean content you can reuse in downstream Relay steps. Nodes used: Schedule -> Olostep Scrape Website
Step 1: Add a schedule trigger
Create a workflow and add a schedule trigger (for example, every weekday at 8 AM).Step 2: Add Olostep Scrape Website
Add an Olostep step and select Scrape Website. Set:- URL:
https://competitor.com/blog - Output Format: Markdown
Step 3: Test and publish
Run a test to confirm the output, then publish or turn on the workflow.What you get
Every run produces clean page content ready for analysis or routing:Scrape Result
- Source URL
- Retrieved content in your selected format
- Timestamped run output in Relay
Parsers
Add a parser ID to the Parser field on the Scrape action to get structured data instead of raw content:| Parser | Extracts |
|---|---|
@olostep/amazon-product | Title, price, rating, reviews, images, variants |
@olostep/google-search | Result titles, URLs, snippets |
@olostep/google-maps | Business name, address, rating, reviews |
@olostep/extract-emails | Email addresses from any page |
@olostep/extract-socials | Social profile links (X, GitHub, LinkedIn, etc.) |
@olostep/extract-calendars | Google Calendar and ICS links |
Relay.app vs Zapier
Relay.app is a strong alternative to Zapier for workflows that need built-in review and AI-first orchestration. Relay.app advantages:- Human-in-the-loop: native approval and review steps in the workflow
- AI-first workflow design: easier to add AI decisions and summaries as first-class steps
- Workflow clarity: clean visual builder with clear run context and step outputs
- You need coverage for a niche app only available on Zapier
- Your team already has many existing Zaps and operational tooling around Zapier
Troubleshooting
API key rejected
API key rejected
Copy the key directly from olostep.com/dashboard with no trailing spaces. Reconnect the Olostep account in Relay if the error persists.
Scraped content is empty
Scraped content is empty
Increase Wait Before Scraping (try 2000–5000ms for JS-heavy pages). Confirm the URL is publicly accessible without login. If one domain consistently fails, contact info@olostep.com.
Rate limit hit
Rate limit hit
Add delays between scrape-heavy runs and retry with backoff for large workflows. Check current usage in the dashboard.
Map step takes longer than expected
Map step takes longer than expected
Maps are async. Store the returned
map_id first, then fetch results in a later step/run once processing is complete.Related
Scrapes API
Full reference for the scrape endpoint
Batches API
How batch jobs work and how to retrieve results
Crawls API
Crawl configuration and result retrieval
Maps API
URL discovery and filtering options