Repository navigation
Conversation
Scrape URL, Extract Structured Data, Get Account Usage and Custom API Call, rendered from platforms/activepieces/ into dist/activepieces/, the piece as it sits in activepieces' packages/pieces/community/zenrows. Its error hints quote the shared/text/ facts the skills use.
… repo scripts/check.sh copies dist/activepieces/ into an activepieces checkout pinned in vars.yaml and runs their lint, build and test for the piece; a path-filtered workflow runs it.
smoke.sh asks for the API key, builds the piece in the activepieces checkout and runs smoke.ts: the four actions on real pages, plus a wrong key and a protected page that must be rejected with their code. Not in CI; it spends credits.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Zenrows piece for Activepieces, the repo's first code host:
platforms/activepieces/renders todist/activepieces/, the piece exactly as it would sit in theirpackages/pieces/community/zenrows. Stacked on #11, which has the host-ownedscripts/folder and the shared error wording; GitHub retargets it tomainwhen #11 merges.Four actions behind an API-key connection: Scrape URL (Markdown, HTML, text or a screenshot; 5 options, Adaptive Stealth Mode on by default), Extract Structured Data (CSS selectors or Automatic, which returns the parsed data), Get Account Usage, and Activepieces' standard Custom API Call for everything else.
Kept lean on purpose. The API validates option combinations and explains every error, so the piece doesn't repeat that. Error messages carry the API's code and reason, plus a hint for the two credit codes, whose wording comes from
shared/text/(the same facts the skills state).Checked three ways:
scripts/check.sh, run by CI: their lint and TypeScript build, inside an Activepieces checkout pinned invars.yaml.scripts/smoke.sh, run by hand with an API key: every action against the live API, plus a wrong key and a protected page that must be rejected with their code. 10 of 10 on 12 Nov. It found two bugs that are fixed here.npm run render -- --check,npm run validate,npm test.Not in this PR: publishing. Activepieces has paused outside PRs since July, so the channel (our own npm package, or their repo once they agree) is GTM's call, tracked on the Linear ticket. The logo is served from this repo until they host it. A manual pass in their UI (
AP_DEV_PIECES=zenrows) is the last step before publishing. Theapi:declaration for #10's spec check comes with the next merge ofmain.