afterwards navigate to a different page on that website using a URL (which requires being logged in first),
GET all the html code
Convert it to a string
find the word 'connected' in this string
have a debug message with a bool showing if 'connected' was found or not
I can link this to an email notification via smtp later, with an existing and configured email node
I tried experimenting with a HTML node that searches for a specific CSS selector but in all cases it couldn't find it or it returned an empty array while it certainly is not.
Any help or example flows on this would be helpful. I need to add this flow to the existing ones which where set up by someone who left the project team and I am new to Node-RED.
I need help with #6 (finding the word 'connected' in the string) and with #3, navigating to a different page after logging in. I don't know how to place my nodes for that. Would two http request nodes in a row work for this? One logging in and one navigating to a nested page on that website?
Yes, you can make two http request node calls in a row, but you may need to clear the msg.req and/or msg.res properties between calls (at least, you used to). Otherwise, the second node tries to reuse some of the first node's properties. I'm guessing that only Nick would have a definitive answer for why this is (or no longer is) necessary... but if the second call fails, you could try using a change node to delete those properties after the first call.