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

@aipowergrid/n8n-nodes-aipg

v0.1.3

Published

AI Power Grid text, image, video, and audio generation for n8n

Readme

n8n Nodes for AI Power Grid

Use AI Power Grid in n8n workflows for text, image, video, and audio generation. The node discovers currently advertised models instead of shipping a stale model catalog.

Credentials

Create a server-side API key in the Grid console. The key needs the account.read and inference.submit scopes carried by ordinary programmatic keys. account.read lets n8n validate the credential without spending credit; inference.submit authorizes generation. Add it to an AI Power Grid API credential in n8n. n8n stores the secret and adds it as a bearer token. The key is never a workflow field.

Do not put the key in browser code, workflow JSON, expressions, prompts, or screenshots. Give production workflows a separate, revocable key with only the scopes they need.

Operations

  • Generate Text calls /v1/chat/completions and returns the completed OpenAI-style response. Standard n8n node executions do not relay SSE to the editor, so this operation deliberately uses stream: false.
  • Generate Image calls /v1/images/generations for text-to-image. The first package does not claim img2img support because binary source handling needs a dedicated upload contract. Its model picker includes only workers advertising txt2img.
  • Generate Video calls /v1/videos/generations for text-to-video. Its model picker excludes workers advertising only img2video.
  • Generate Audio calls /v1/audio/generations for ACE-Step music, with optional lyrics and governed controls.

Image, video, and audio executions wait for the worker result and return the Grid response, including result URLs and provenance metadata. Their request timeouts follow Core's current modality deadlines. Use n8n queue mode and worker execution timeouts appropriate for long media jobs.

Example workflows

  • Support draft: Manual Trigger -> AI Power Grid (Generate Text) -> Slack. Map the incoming support message into Prompt, then send choices[0].message.content to Slack for review.
  • Campaign artwork: Schedule Trigger -> AI Power Grid (Generate Image) -> HTTP Request. Generate one image, then download the first returned result URL into n8n binary data for the next publishing step.
  • Podcast bumper: Form Trigger -> AI Power Grid (Generate Audio) -> cloud storage. Map the submitted style notes into Music Description, use a short bounded duration, and store the returned audio URL.

Start with a Manual Trigger while building a workflow. Run one item, inspect the Grid response in the output panel, and map only the fields needed by the next node. Availability is dynamic, so select a currently advertised model instead of relying on an old saved model name.

Errors and credits

Grid HTTP errors are surfaced as n8n node errors. Common statuses are:

  • 401: invalid or revoked API key
  • 402: insufficient usable credits
  • 404: model no longer available
  • 422: request or model parameter is unsupported
  • 429: rate or concurrency limit reached
  • 503: no compatible worker is online

Fund the same Grid account at console.aipowergrid.io. Retry only operations your workflow can safely repeat; a media timeout does not prove that the remote job failed.

Privacy and positioning

Grid requests are routed to remote community-operated workers. Workers may be able to inspect plaintext prompts, source material, and outputs. Do not send secrets, personal or regulated data, or confidential source code unless a separately verified confidential-compute deployment satisfies your needs.

This package is maintained by AI Power Grid. It does not imply a partnership with or endorsement by n8n.

Development

Node.js 22 or newer is required.

npm ci
npm test
npm run lint
npm run build
npm pack --dry-run

A credentialed release check must exercise one bounded request in every operation before publication. Those checks spend account credit and are not part of the default test suite:

AIPG_LIVE_E2E=1 npm run test:e2e:live

Use a disposable account.read + inference.submit key and revoke it after the run. The live test does not print the key, prompts, generated media URLs, model output, or account balance.

Release

@aipowergrid/[email protected] is the current public package. Version 0.1.3 moves its npm provenance to this dedicated repository so n8n's Creator Portal can resolve credential source files at the repository root. Release it only through .github/workflows/publish.yml and the npm OIDC Trusted Publisher for this repository. The workflow rejects a tag that does not exactly match package.json, requires the release commit to be on main, and reruns the package checks before publishing. The one-time bootstrap token is revoked; do not restore a registry token.