# Trigger / Expression Editor keyboard friendliness

**URL:** <https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627>\
**Category:** Product Suggestions\
**Tags:** feature-request\
**Created:** [October 6, 2026, 1:10am UTC](https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627 "2026-10-06T01:10:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![enewton](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/enewton/32/9518_2.png) [@enewton](https://community.tulip.co/u/enewton)\
**Post date:** [October 6, 2026, 1:10am UTC](https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627/1 "2026-10-06T01:10:57Z")

</div>

Hello,

I am trying to learn to program trigger logic without needing to click and move the mouse so much, but it’s rather difficult. I see that it’s clearly possible to an extent, but there is a lot of unintuitive tabbing and fumbling required to even try.

I would be very pleased to see the trigger editor flow smoothly using the keyboard only.  
I currently can’t automatically select the next field when the previous one is filled in. When I find the right option from the drop down and press enter or tab, the next field is red and unselected. The number of times I need to press tab after that seems to vary. It’s not consistent. Some cases, like for table record options, I can start typing a record placeholder name or table field, and it will actually select the first one that matches the first letter and then unfocus, so I can’t keep typing but I also can’t enter the next field.

In general, being able to start typing variable names and then tab to autocomplete with the highlighted match, would be an incredible feature for both trigger editor and expression editor.

For now, I will keep using the mouse because the randomness of using the keyboard makes it take longer. However, if I could use the keyboard as I describe, I would be able to work many times faster.

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [October 6, 2026, 7:13am UTC](https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627/2 "2026-10-06T07:13:47Z")

</div>

Don’t forget to vote for your own suggestion 😉

---

<div class="post-metadata">

**Author:** ![enewton](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/enewton/32/9518_2.png) [@enewton](https://community.tulip.co/u/enewton)\
**Post date:** [October 6, 2026, 5:18pm UTC](https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627/4 "2026-10-06T17:18:19Z")

</div>

Aha! Thank you. I didn’t realize it’s not like reddit

---

<div class="post-metadata">

**Author:** ![atrabuco](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/atrabuco/32/9497_2.png) [@atrabuco](https://community.tulip.co/u/atrabuco)\
**Post date:** [October 15, 2026, 2:54pm UTC](https://community.tulip.co/t/trigger-expression-editor-keyboard-friendliness/16627/5 "2026-10-15T14:54:58Z")

</div>

Hey @enewton , thanks for the detail here. Keyboard navigation matters to us, including for accessibility, so the inconsistent tabbing and focus you’re describing is good to have written down. A fuller keyboard-driven flow, like typing to autocomplete across fields, isn’t something we’re planning right now. The closest thing we’re looking at is better search in the expression editor, so you can type part of a name and find it without the full path (see [UX improvements to expression editor](https://community.tulip.co/t/ux-improvements-to-expression-editor/16544)). This is something we will look to tackle, and when changes come I’ll be sure to let you know here.