No description
Find a file
2025-07-06 18:44:45 -05:00
.vscode Track .vscode dir 2022-07-14 14:59:38 +02:00
credentials S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
nodes S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
.editorconfig add TOC and version history section 2022-08-17 16:41:50 +01:00
.env fix: .env file added 2025-06-22 21:51:38 -05:00
.eslintrc.js Update to support new features (#70) 2025-05-13 14:26:01 +01:00
.eslintrc.prepublish.js 👕 Update lint config 2022-12-29 17:56:50 +01:00
.gitignore Add package-lock.json to versions 2022-07-11 15:52:39 +02:00
.npmignore Add .npmignore 2022-12-29 17:55:47 +01:00
.prettierrc.js 🔧 Create Prettier config 2022-06-27 11:44:09 +02:00
CODE_OF_CONDUCT.md update readme and add CoC 2022-08-11 10:18:01 +01:00
cursor_nodo_personalizado.md S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
deploy-node.sh S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
docker-compose.yml S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
gulpfile.js Make paths OS-agnostic 2022-06-28 15:25:17 +02:00
index.js S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
LICENSE.md readme template draft 2022-08-17 16:10:14 +01:00
package-lock.json chore: ExampleNode2 added 2025-06-23 21:39:13 -05:00
package.json S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
README.md fix: pnpm added to README.md 2025-06-22 21:54:54 -05:00
README_S4DS.md S4DSAuth node added. Some other nodes deleted 2025-07-06 18:44:45 -05:00
README_TEMPLATE.md docs: update section links (#71) 2025-05-16 12:19:17 +01:00
tsconfig.json 🔧 Update tsconfig.json 2022-12-29 17:56:39 +01:00

Banner image

n8n-nodes-starter

This repo contains example nodes to help you get started building your own custom integrations for n8n. It includes the node linter and other dependencies.

To make your custom node available to the community, you must create it as an npm package, and submit it to the npm registry.

If you would like your node to be available on n8n cloud you can also submit your node for verification.

Prerequisites

You need the following installed on your development machine:

  • Docker and Docker Compose
  • NodeJS, npm and pnpm (Execture npm install -g pnpm@latest-10 after installing npm)

Once you have cloned the repository:

  • Execute:
    npm i
    

To run the local n8n instance:

When changes are made to the custom node code and you want to test it on the local instance:

  • There is a script file called deploy-node.sh. Once executed, it will build the custom node code and deploy the Docker container. This file requires a few changes depending on the name that Docker gives to the container and the volumes:

    • On line 24 of the script, you will see this line:

      TARGET_DIR="/var/lib/docker/volumes/n8n-self-hosted_n8n_data/_data/custom/$PACKAGE_NAME"
      
    • Depending on the container volume name, "n8n-self-hosted_n8n_data" needs to be changed. To check the volume's name, execute:

      docker volume ls
      
    • On lines 56 and 59, "n8n-self-hosted-n8n-1" must be changed to match the name of the container for the n8n instance.

    • Once these changes are made, execute the script:

      ./deploy-node.sh
      

Using this starter

These are the basic steps for working with the starter. For detailed guidance on creating and publishing nodes, refer to the documentation.

  1. Generate a new repository from this template repository.
  2. Clone your new repo:
    git clone https://github.com/<your organization>/<your-repo-name>.git
    
  3. Run npm i to install dependencies.
  4. Open the project in your editor.
  5. Browse the examples in /nodes and /credentials. Modify the examples, or replace them with your own nodes.
  6. Update the package.json to match your details.
  7. Run npm run lint to check for errors or npm run lintfix to automatically fix errors when possible.
  8. Test your node locally. Refer to Run your node locally for guidance.
  9. Replace this README with documentation for your node. Use the README_TEMPLATE to get started.
  10. Update the LICENSE file to use your details.
  11. Publish your package to npm.

More information

Refer to our documentation on creating nodes for detailed information on building your own nodes.

License

MIT