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

@petretiandrea/n8n-nodes-codex

v0.1.1-2

Published

n8n community node for OpenAI Codex via ChatGPT subscription device-code auth

Downloads

20

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

petretiandreapetretiandrea

Keywords

n8n-community-node-packagen8ncodexopenai

Readme

n8n Codex Community Node

Community node package for using OpenAI Codex in n8n through the ChatGPT subscription device-code flow.

MVP scope

  • Self-hosted n8n only
  • Device-code bootstrap helper
  • Codex Chat Model AI root node
  • Text generation with optional streaming
  • Runtime access-token refresh using the stored refresh token bundle

Important caveat

This package talks to the internal Codex backend currently exposed at https://chatgpt.com/backend-api/codex/responses. It is not the public OpenAI API and may change without notice.

Authentication

The current n8n credential UI does not provide a first-class interactive device-code login flow for community nodes, so this package ships a helper CLI:

npx --package @petretiandrea/n8n-nodes-codex codex-device-login

Run it, complete authorization in the browser, then paste the returned values into the Codex Device Auth API credential.

Publishing

This package supports both the official n8n-node release flow and GitHub Actions publishing.

First local release

For the first publish, the simplest path is:

npm login
npm run release

n8n-node release uses release-it to run lint and build checks, update the changelog, create git tags, create a GitHub release, and publish the package to npm.

Before running it, make sure the repository has a valid GitHub remote configured and that you have publish access to the @petretiandrea/n8n-nodes-codex package on npm.

GitHub Actions publish

  1. Push the repository to GitHub.
  2. In GitHub repository settings, add the NPM_TOKEN secret with an npm automation token that has publish access for @petretiandrea/n8n-nodes-codex.
  3. Create a GitHub release or push a version tag like v0.1.0.
  4. The workflow at .github/workflows/publish.yml will run tests, build the package, and publish it to npm.

After publishing, users can install the package in self-hosted n8n and run:

npx --package @petretiandrea/n8n-nodes-codex codex-device-login

to bootstrap the credential values.

Known limitations

  • No tool calling yet
  • No multimodal support yet
  • No n8n Cloud target yet
  • Refresh tokens are reused at runtime, but if the backend rotates them you may need to run the bootstrap helper again