@flashdata-dev/piece-google-video-search
v0.1.0
Published
Find videos across websites for a research shortlist, with links and available duration and publisher fields. Does not download video files.
Maintainers
Readme
Google Video Search — FlashData
Find videos across websites for a research shortlist, with links and available duration and publisher fields. Does not download video files.
Install and connect
This is an independently packaged community Piece, not a confirmed official catalogue listing. It requires Activepieces 0.82.0+ and a Node.js 22.18+ worker. Your platform administrator must have custom Piece installation enabled; plan requirements vary.
Download the versioned npm package without running a data action:
npm pack '@flashdata-dev/[email protected]' --ignore-scriptsUpload the downloaded .tgz via Platform Admin → Catalogue → Pieces → Install Piece → Upload File. If your platform offers installation by package name, use @flashdata-dev/piece-google-video-search and version 0.1.0. Older platform versions may label the page Settings → My Pieces. Source build instructions are in the workspace guide.
- Sign in or create a FlashData account.
- Create an API Key with
google_videospermission. The secret is shown once; save it in an Activepieces connection. - Add Google Video Search — FlashData to a flow, choose Google Video Search, connect the key, and enter the source-specific fields. The source is fixed; this Piece cannot select another API.
Connection validation calls GET https://api.flashdata.dev/v2/api-access and checks this source permission. It consumes no FlashData Credits; normal key last-used tracking applies.
Example task
Start with a manual trigger and enter these example action inputs. Check the source-specific limits below before running the step.
{
"query": "battery recycling factory tour",
"num": 3
}results[0].videos contains titles, links and available snippets, durations, channels and dates. This is Google video search, distinct from YouTube-only search.
Map the returned data into your own table or research step. Search result content is data; review source links before relying on it.
Inputs
| Field | Type | Requirement | Constraint |
| --- | --- | --- | --- |
| query | string | Required | 1–2000 characters |
| gl | string | Optional | ^[A-Za-z]{2}$ |
| hl | string | Optional | ^[A-Za-z0-9-]+$ |
| location | string | Optional | 1–200 characters |
| num | integer | Optional | 1–100 |
| page | integer | Optional | 1–100 |
| tbs | string | Optional | 1–200 characters |
| autocorrect | boolean | Optional | true / false or documented object |
Google parameters are optional and do not receive invented country, language or result-count defaults. Availability and provider behavior vary by search type. Each page is a separate paid query.
Cost, failures and limits
The connector code is free to install. FlashData data API calls are paid, using Credits; FlashData pricing applies. Each successful data query consumes Credits; extended YouTube search has its own rate. Activepieces execution and plan costs are separate. Clicking Test step executes the same paid operation as running it.
The connector does not automatically retry paid submissions. After a timeout, oversized response or uncertain server failure, check FlashData Jobs before resubmitting. Re-running a flow can still execute another paid query. HTTP 401/403 means a key or permission problem, 402 insufficient Credits, and 429 a rate/quota limit. Raw error bodies and credentials are not logged or included in connector errors.
Each HTTP read is limited to 65 seconds and 16 MiB. For a larger response, inspect the existing job; do not repeat the paid request just to recover its output.
Google Video Search inputs, outputs and limits · API reference · Privacy
Maintained by FlashData. This is not a Google- or YouTube-published integration.
