Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Scrapeless

Scrapeless is an all-in-one and highly scalable web scraping toolkit for enterprises and developers.

CategoryProductivity
Authenticationcustom
Version0.2.1
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Scrapeless with Flows360

Scrapeless is an all-in-one and highly scalable web scraping toolkit for enterprises and developers.

Use the Scrapeless connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Google Search
  • Scrape Webpage Data
  • Crawl Data from All Pages
  • Google Trends
  • Universal Scraping
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Scrapeless
  • Package: @activepieces/piece-scrapeless@0.2.1
  • Exact artifact digest: sha256:d21a62fd7462e3119187d5004edbd973199fbc8eccf088e951c5e91b04f9ce3b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Google Search (google_search_api), Retrieves search result data for any query. Classification: read.
  • Scrape Webpage Data (crawl_scrape), Extracts data from a single webpage. Classification: read.
  • Crawl Data from All Pages (crawl_crawl), Crawls a website and its linked pages to extract comprehensive data. Classification: read.
  • Google Trends (google_trends_api), Access popular keyword and interest data from Google Trends. Classification: read.
  • Universal Scraping (universal_scraping_api), Seamlessly accesses protected or dynamic pages by handling anti-scraping systems automatically. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Google Search Yes No Retrieves search result data for any query.
Scrape Webpage Data Yes No Extracts data from a single webpage.
Crawl Data from All Pages Yes No Crawls a website and its linked pages to extract comprehensive data.
Google Trends Yes No Access popular keyword and interest data from Google Trends.
Universal Scraping Yes No Seamlessly accesses protected or dynamic pages by handling anti-scraping systems automatically.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Google Search · Read

Retrieves search result data for any query.

google_search_api · Risk: low · Retry: safe

Inputs

  • q · string · Required, Parameter defines the query you want to search. You can use anything that you would use in a regular Google search. e.g. inurl:, site:, intitle:. We also support advanced search query parameters such as as_dt and as_eq.
  • hl · string · Optional, Parameter defines the language to use for the Google search. It's a two-letter language code. (e.g., en for English, es for Spanish, or fr for French).
  • gl · string · Optional, Parameter defines the country to use for the Google search. It's a two-letter country code. (e.g., us for the United States, uk for United Kingdom, or fr for France).
Scrape Webpage Data · Read

Extracts data from a single webpage.

crawl_scrape · Risk: low · Retry: safe

Inputs

  • url · string · Required, The URL of the webpage to scrape.
Crawl Data from All Pages · Read

Crawls a website and its linked pages to extract comprehensive data.

crawl_crawl · Risk: low · Retry: safe

Inputs

  • url · string · Required, The URL of the webpage to crawl.
  • limit · number · Required, Number Of Subpages
Google Trends · Read

Access popular keyword and interest data from Google Trends.

google_trends_api · Risk: low · Retry: safe

Inputs

  • q · string · Required, Parameter defines the query or queries you want to search. You can use anything that you would use in a regular Google Trends search. The maximum number of queries per search is 5 (this only applies to `interest_over_time` and `compared_breakdown_by_region` data_type, other types of data will only accept 1 query per search).
  • data_type · string · Required, Parameter defines the type of data you want to search. You can use anything that you would use in a regular Google Trends search. The maximum number of queries per search is 5 (this only applies to `interest_over_time` and `compared_breakdown_by_region` data_type, other types of data will only accept 1 query per search).
  • date · string · Required, The supported dates are: `now 1-H`, `now 4-H`, `now 1-d`, `now 7-d`, `today 1-m`, `today 3-m`, `today 12-m`, `today 5-y`, `all`.You can also pass custom values:Dates from 2004 to present: `yyyy-mm-dd yyyy-mm-dd` (e.g. `2021-10-15 2022-05-25`)nDates with hours within a week range: `yyyy-mm-ddThh yyyy-mm-ddThh` (e.g. `2022-05-19T10 2022-05-24T22`). Hours will be calculated depending on the tz (time zone) parameter.
  • hl · string · Optional, Parameter defines the language to use for the Google Trends search. It's a two-letter language code. (e.g., `en` for English, `es` for Spanish, or `fr` for French).
  • tz · string · Optional, time zone offset. default is `420`.
Universal Scraping · Read

Seamlessly accesses protected or dynamic pages by handling anti-scraping systems automatically.

universal_scraping_api · Risk: low · Retry: safe

Inputs

  • url · string · Required
  • js_render · boolean · Optional
  • headless · boolean · Optional
  • country · string · Optional
  • js_instructions · object · Optional
  • block · object · Optional
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Scrapeless connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-scrapeless@0.2.1; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Scrapeless connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-scrapeless@0.2.1 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com