As far as I can remember there always used to be a “begins with” and “ends with” option in the switch node, but there’s not anymore. Has anyone of you a clue where this feature has gone or whether I’m only hallucinating things?
Hey @nm5182, while you wait for a response, here are some things that might help:
Automatically matched to your question.
Docs:
Forum:
@jabbson, @eneighten1000 - you’ve helped with similar issues before, can you take a look?
Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.
Hi @nm5182
They’re still there. The String submenu scrolls and its scrollbar is hidden, so the list just fades out after “contains”. Scroll inside that submenu with the wheel or the arrow keys and you get “does not contain”, “starts with”, “does not start with”, “ends with”, “does not end with” and the two regex ones.
Worth fixing while you’re in there: {{ $json.statusCode }} is flagged red because the value is a number and the operator is set to String. Turn on the “Convert types where required” toggle below the rules, or move that condition to Number.
If it’s not showing up in your UI, it could be due to:
Attribute/Field Configuration - In the Switch node, you need to make sure you’re selecting a String data type attribute (or a field that has a string value). If the data type detector thinks the field is JSON or a different type, it might limit the available operators.
UI Translation - If you have n8n set to a non-English language, these might be translated.
Field Values - The feature is there, but if your input data is empty, the comparisons like “is empty” might behave unexpectedly.
Does any of these apply?
Wooow. First of all thanks! How would anybody think when there’s absolutely no indicator that there are no options that there would be more options?
No part of the next entry, no scrollbar, no fade at the bottom to indicate “hey, there’s more!”.
Do you know why n8n made this design choice? As a user I need at least some indicator that there’s more. 
Not a design choice as far as I can tell, more of a paper cut. That submenu is a plain overflow container relying on the browser’s overlay scrollbar, which on Windows Chrome only paints while you hover or scroll, so at rest there is nothing to see. In your second screenshot the thumb is just about visible as a grey sliver at the top right and bottom right of the panel, and that is the entire indicator.
A persistent scrollbar or a fade on that submenu would be a small change and this trips people up often enough to be worth raising:
