Screenshot a webpage and send email using nodered

can i actually take webshot of a webpage then email it using nodered? i did try to use the webshot palette...but it keep on crashing whenever i trigger it. Crashing means.....i will be logout from my Node-RED

If a node crashes Node-RED you really need to tell the author (usually by opening an issue on the nodes github page) so that it can be fixed.

There is also the nbrowser contrib node which you can find and read the readme on glows.nodered.org

haha, interesting idea for a website :wink:

However, flows.nodered.org might give some better results for now. :smile:

1 Like

To get more information run

node-red-stop
node-red-start

in a terminal, then trigger the node. You can post the resulting output here if necessary.

I can verify that the webshot node crashes and restarts Node-RED. I too am looking for a way to capture a Node-RED ui screenshot and send it, via Twilio/SMS. I've tried all 3 nodes that mention screenshots, including the one that came out today. The other two I've tried are node-red-contrib-screenshot 1.0.1 and today's version of node-red-contrib-web-page-screenshot 0.0.2. Here's the output after installing webshot and adding it to a flow:

9 May 14:56:09 - [info] Installed module: node-red-contrib-webshot
9 May 14:56:10 - [info] Added node types:
9 May 14:56:10 - [info] - node-red-contrib-webshot:WebShot
Prelimenary Heat Index is 87.13989869999992
Heat index with no adjustment is 87.13989869999992
Prelimenary Heat Index is 87.13989869999992
Heat index with no adjustment is 87.13989869999992
9 May 14:56:54 - [info] Stopping modified nodes
9 May 14:56:54 - [info] Stopped modified nodes
9 May 14:56:54 - [info] Starting modified nodes
9 May 14:56:54 - [info] Started modified nodes
9 May 14:57:48 - [red] Uncaught Exception:
9 May 14:57:48 - Error: spawn phantomjs ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:362:16)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
9 May 14:57:52 - [info]
Welcome to Node-RED

9 May 14:57:52 - [info] Node-RED version: v0.20.5
9 May 14:57:52 - [info] Node.js version: v8.16.0
9 May 14:57:52 - [info] Linux 4.14.98-v7+ arm LE
9 May 14:57:52 - [info] Loading palette nodes
9 May 14:58:04 - [info] Worldmap version 1.5.38
9 May 14:58:08 - [info] Dashboard version 2.9.8 started at /ui
9 May 14:58:10 - [info] Settings file : /home/pi/.node-red/settings.js
9 May 14:58:10 - [info] HTTP Static : /home/pi/.node-red/public
9 May 14:58:10 - [info] Context store : 'default' [module=memory]
9 May 14:58:10 - [info] User directory : /home/pi/.node-red
9 May 14:58:10 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 May 14:58:10 - [info] Flows file : /home/pi/.node-red/flows.json
9 May 14:58:10 - [info] Server now running at http://127.0.0.1:1880/
9 May 14:58:10 - [warn]