npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ever-works/activepieces-plugin

v1.0.18

Published

Activepieces Automation Pipeline Plugin - Delegates Work generation steps to Activepieces flows

Readme

@ever-works/activepieces-plugin

Activepieces Automation Pipeline Plugin - Delegates Work generation steps to Activepieces flows

Plugin metadata

| Field | Value | | ------------ | ---------------------------------- | | ID | activepieces | | Category | pipeline | | Capabilities | pipeline, form-schema-provider | | Author | Ever Works Team | | License | AGPL-3.0 | | Built-in | yes | | Auto-enable | no |

What does the Activepieces plugin do?

This plugin lets Ever Works delegate the work-generation pipeline to Activepieces, an open-source, AI-first automation platform available as both a managed cloud service and a self-hosted deployment. Instead of running the built-in pipeline, Ever Works hands each generation request off to an Activepieces flow that you design visually in the Activepieces builder.

You author a flow with a webhook trigger (and a Return Response action for synchronous output), wire up whatever pieces you need — AI providers, search APIs, scrapers, databases, custom code blocks — and the plugin invokes that flow during work generation. The flow returns structured JSON that Ever Works converts into pipeline outputs (the work draft, items list, categories, tags, brands).

Why use it?

  • Tap into Activepieces' library of pre-built pieces for hundreds of SaaS apps, databases, and AI services without writing integration code.
  • No-code visual flow builder — non-developers on your team can iterate on the generation logic.
  • Self-host Activepieces alongside Ever Works for full data residency and zero per-task vendor cost, or use Activepieces Cloud.
  • Swap in custom logic, branching, retries, or human-in-the-loop steps without touching Ever Works code or redeploying.
  • Reuse existing Activepieces flows, pieces, and connections you already maintain for other automations.

How it works in Ever Works

When this plugin is selected as the active pipeline, the platform sends each generation request to your configured Activepieces flow via its webhook trigger (using the Activepieces REST API and your platform API key). The flow runs in Activepieces — optionally calling AI providers, search APIs, scrapers, etc. — and returns a structured JSON response through its Return Response action. The plugin parses that response back into Ever Works pipeline outputs (the work draft, items list, categories, tags). The required output schema is documented in the Ever Works docs.

Getting started

  1. Sign up for Activepieces Cloud or deploy a self-hosted instance (Platform or Enterprise edition is required to issue API keys).
  2. In your Activepieces dashboard, create a new flow with a Webhook trigger and a Return Response action that emits the JSON shape Ever Works expects.
  3. Generate a Platform API key from the Activepieces dashboard and note your project ID and the flow ID.
  4. Open the Activepieces plugin settings in Ever Works and paste the API key, project ID, and default flow ID. Save.
  5. Trigger a run from the Generate flow and inspect the run record in the Activepieces dashboard if anything goes wrong.

Settings

  • apiKey (secret) — Activepieces Platform API key. Required.
  • baseUrl — Activepieces API base URL. Defaults to Activepieces Cloud; override for self-hosted instances.
  • projectId — Default project ID used to scope flow listings and run inspection.
  • defaultFlowId — Flow ID invoked when the generator form does not specify one.

The generator form additionally exposes per-run options including the flow ID override, sync/async webhook mode, target item count, flow timeout, repository access pass-through, and custom flow parameters.

Troubleshooting

| Symptom | Likely cause | Fix | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Generation never starts / stays at 0% | activepieces not selected as the active pipeline plugin for this work | Open the work → Plugins → pipeline capability and set activepieces as the active pipeline; or set it as the global pipeline default in Settings → Plugins | | Step fails with No AI / search / screenshot provider configured | Pipeline depends on capability plugins that are not enabled or have no credentials | Enable and configure the matching capability plugin (AI provider, search, screenshot, content-extractor) for the work or globally | | Step output looks wrong / generic | Form-field tuning not set; pipeline using defaults that don't match the work's domain | Open the Generator Form for the work, set domain-specific fields (categories, target keywords, source URLs), and re-run the affected step | | Webhook returns 404 / Not Found | Scenario / Zap not enabled or webhook URL stale | In the Activepieces Automation dashboard verify the scenario is active, copy a fresh webhook URL into the plugin settings, and trigger a test run | | Pipeline cannot resume after host restart | Checkpoint not persisted (only the standard pipeline persists checkpoints today) | Cancel the stuck run and re-trigger generation; for production reliability prefer standard-pipeline |

Local development

This plugin ships built-in with the Ever Works platform. To work on it locally from the monorepo root:

pnpm install
pnpm --filter @ever-works/activepieces-plugin build
pnpm --filter @ever-works/activepieces-plugin test

Documentation

License

AGPL-3.0