How drudge/n8n-nodes-puppeteer works
Project type and purpose
• This is a community-maintained n8n node package (“n8n-nodes-puppeteer”) that extends the n8n workflow automation platform to perform browser automation via Puppeteer.
• The node sits inside an n8n installation, exposing operations such as “Get Page Content,” “Get Screenshot,” “Get PDF,” and “Custom Script” to end users.
File structure
• Top-level files:
• index.js – Entry point that registers the Puppeteer node(s) with n8n
• package.json, tsconfig.json, tslint.json – Configuration & metadata
• Dockerfile + docker/ folder – Prebuilt container for production usage
• nodes/Puppeteer/ – TypeScript source for the Puppeteer integration
• Puppeteer.node.ts – Definition of the node’s operations & parameters
• Puppeteer.node.options.ts – Option schema for each operation
• types.d.ts – Shared type definitions
• gulpfile.js – Build tasks (compile TS, copy assets)
• .github/workflows/publish.yml – CI/CD pipeline for publishing to npm
README for additional insights
• Explains two deployment modes:
a. Local installation as an n8n community node
b. Dockerized image hosting both n8n and Puppeteer with required dependencies
• Describes runtime options: local browser vs. remote WebSocket endpoint
Elements
• Clear labels: “n8n Core,” “Puppeteer Node,” “Puppeteer Library,” “Browser Instance,” “Docker Host”
• n8n → Plugin → Puppeteer → Browser
• Browser → Plugin → n8n
• (Optional) Plugin → Remote Browser Service
• Rectangles for compute components (n8n, Plugin, Browser)
• Container boundary to enclose Dockerized components