# Upcoming Changes to Backend Workflow Location

**URL:** <https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960>\
**Category:** New features\
**Created:** [November 26, 2024, 9:23pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960 "2024-11-26T21:23:01Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![kate.mcnally](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/kate.mcnally/32/204999_2.png) [@kate.mcnally](https://forum.bubble.io/u/kate.mcnally)\
**Post date:** [November 26, 2024, 9:23pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/1 "2024-11-26T21:23:01Z")

</div>

Hi there, Bubble community.

I’m Kate, a product manager at Bubble. We have an exciting update coming your way, and we want to make sure you know about it ahead of time to set you up for a smooth transition! Starting in the next month or so, the **Bubble Editor’s navigation menu will make it easier to access backend workflows**. This change is designed to simplify and improve the way you use Bubble, whether you’re new to Bubble or a seasoned pro.

In the current experience, the **backend workflows UI** can only be found by enabling a checkbox in **settings** and then scrolling to the bottom of the **pages and reusables dropdown**. This is hard for inexperienced users to navigate and is annoying for those who are already used to the system.

Backend workflows are key to the building experience, so we’re making them a first-class feature in the editor. Here are more details:

**What’s changing?**

Starting in mid / late December, **backend workflows** will appear in the left-hand navigation alongside **design** , **workflows** , and **data** , for all users regardless of participation in the Workflow Tab Beta.

 ![backend_workflows](https://us1.discourse-cdn.com/bubble/original/3X/d/8/d840f0a83f7bcb98f49f80c8493f04e4a64ed8b4.png)

The **backend workflows tab** will always be visible within the editor. You’ll no longer need to enable or disable access to the **backend workflow UI** in **settings**. Now, the setting Enable Workflow API will only control the access for other apps and systems to trigger API workflows in your app. (Note that this setting will be enabled by default for all new apps and will work on any app on the Starter plan or above.)

Alongside this navigational change, you will see a change in the URL paths for tabs of the Bubble Editor. Instead of including a tab number, like we have today, the URL will now specifically list the tab name. For example, the Design tab will go from **tab=tabs-1** to **tab=Design**. Any integration or setup you have today will not be affected, as we will continue to redirect any of the previous URL patterns to the new URL.

**How to prepare:** You don’t need to make any changes to your existing apps.

We’re excited to bring this improvement to the Bubble Editor and are confident it will make your building experience more seamless than ever. Thank you for being a part of the Bubble community and for your ongoing support as we continue to enhance our platform.

If you have any questions or concerns about this update, don’t hesitate to respond here! As always, your feedback is invaluable to us. And if you’re noticing something that looks like a bug, please please don’t hesitate to [submit bug reports](https://bubble.io/contact?value=bug-report) through our AI chatbot in the bottom right-hand corner of our Support Center or any [bubble.io](http://bubble.io) page.

Happy building!

Kate,  
Product Manager at Bubble

---

<div class="post-metadata">

**Author:** ![lindsay\_knowcode](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/lindsay_knowcode/32/92967_2.png) [@lindsay\_knowcode](https://forum.bubble.io/u/lindsay_knowcode)\
**Post date:** [November 26, 2024, 9:45pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/2 "2024-11-26T21:45:53Z")

</div>

What was the thinking behind the icon? 2 single beds ?

🙂

---

<div class="post-metadata">

**Author:** ![jo1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jo1/32/262669_2.png) [@jo1](https://forum.bubble.io/u/jo1)\
**Post date:** [November 26, 2024, 9:51pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/3 "2024-11-26T21:51:41Z")

</div>

Good one team! Can’t wait for the top bar overhaul and dark mode 🤞

---

<div class="post-metadata">

**Author:** ![helder](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/helder/32/231491_2.png) [@helder](https://forum.bubble.io/u/helder)\
**Post date:** [November 26, 2024, 10:29pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/4 "2024-11-26T22:29:05Z")

</div>

That icon usually represents ‘’stacked servers”, with the dot being the power button. Make sense to me for their icon choice…

---

<div class="post-metadata">

**Author:** ![Jici](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jici/32/30722_2.png) [@Jici](https://forum.bubble.io/u/Jici)\
**Post date:** [November 26, 2024, 10:39pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/5 "2024-11-26T22:39:24Z")

</div>

Thanks! This make a lot more sense.  
Next: API connector tab?

---

<div class="post-metadata">

**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\
**Post date:** [November 27, 2024, 12:00am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/6 "2024-11-27T00:00:13Z")

</div>

> [@lindsay\_knowcode](#):
>
> 2 single beds ?

C’mon, it’s blatantly obvious. Backend WFs are how you implement a “REST” API in Bubble.

😏  
😆

---

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [November 27, 2024, 12:46am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/8 "2024-11-27T00:46:19Z")

</div>

Please tell me the backend workflow tab will no longer reset after going to the design tab and vice-versa. It’s my single biggest annoyance in the editor.

---

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [November 27, 2024, 12:51am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/9 "2024-11-27T00:51:48Z")

</div>

The icon is technically “correct,” however it’s too similar to database. I would suggest something like:

![Screenshot 2024-11-26 165012](https://us1.discourse-cdn.com/bubble/original/3X/3/0/303bdf519a625d0d6a229f3cca03862d26c79ac0.png)

---

<div class="post-metadata">

**Author:** ![lindsay\_knowcode](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/lindsay_knowcode/32/92967_2.png) [@lindsay\_knowcode](https://forum.bubble.io/u/lindsay_knowcode)\
**Post date:** [November 27, 2024, 9:53am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/10 "2024-11-27T09:53:00Z")

</div>

And I thought my joke was sad … 🤣

@jici It is so true that the API connector is a candidate as a first-class item on the quick navigation menu.

---

<div class="post-metadata">

**Author:** ![MattN](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/mattn/32/100743_2.png) [@MattN](https://forum.bubble.io/u/MattN)\
**Post date:** [November 27, 2024, 10:25am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/11 "2024-11-27T10:25:51Z")

</div>

Thanks @kate.mcnally !

I know I’m banging the drum, but as a first class feature we really need to be able to return data from internal BEWs natively, as this thread illustrates : [Why your backend workflows might be your app’s biggest vulnerability](https://forum.bubble.io/t/why-your-backend-workflows-might-be-your-apps-biggest-vulnerability/348030)

---

<div class="post-metadata">

**Author:** ![boston85719](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/boston85719/32/77286_2.png) [@boston85719](https://forum.bubble.io/u/boston85719)\
**Post date:** [November 27, 2024, 10:32am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/12 "2024-11-27T10:32:06Z")

</div>

No more new tab in the browser! Excellent stuff. Keep them coming!

---

<div class="post-metadata">

**Author:** ![luke2](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/luke2/32/256674_2.png) [@luke2](https://forum.bubble.io/u/luke2)\
**Post date:** [November 27, 2024, 12:20pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/13 "2024-11-27T12:20:38Z")

</div>

100% yes. Over 1 million installs on apps and opens up bubble’s capabilities that on the surface will be hidden to new users without the install.

---

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [November 27, 2024, 12:27pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/14 "2024-11-27T12:27:23Z")

</div>

> [@MattN](#):
>
> Thanks @kate.mcnally !
> 
> I know I’m banging the drum, but as a first class feature we really need to be able to return data from internal BEWs natively, as this thread illustrates : [Why your backend workflows might be your app’s biggest vulnerability](https://forum.bubble.io/t/why-your-backend-workflows-might-be-your-apps-biggest-vulnerability/348030)

Timestamp:  
11m37s

The argument around backend workflows being “less safe” is bizarre to me as people are more likely to put conditions on workflows than properly do serverside page redirects.

[![](https://img.youtube.com/vi/JItxZUEeqlM/maxresdefault.jpg "AMA with Bubble Engineer, Alessandro Jeanteur | Bubblecon 2024") ](https://www.youtube.com/watch?v=JItxZUEeqlM&t=11m37s)

---

<div class="post-metadata">

**Author:** ![prograds](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/prograds/32/260638_2.png) [@prograds](https://forum.bubble.io/u/prograds)\
**Post date:** [November 27, 2024, 7:03pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/15 "2024-11-27T19:03:32Z")

</div>

Big thumbs up on this one.

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [November 27, 2024, 7:17pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/16 "2024-11-27T19:17:59Z")

</div>

Pinned globally on November 27, 2024, 7:17pm UTC



---

<div class="post-metadata">

**Author:** ![jacob2](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jacob2/32/243491_2.png) [@jacob2](https://forum.bubble.io/u/jacob2)\
**Post date:** [November 27, 2024, 7:48pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/17 "2024-11-27T19:48:50Z")

</div>

This is cool

---

<div class="post-metadata">

**Author:** ![jacob2](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jacob2/32/243491_2.png) [@jacob2](https://forum.bubble.io/u/jacob2)\
**Post date:** [November 27, 2024, 7:50pm UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/18 "2024-11-27T19:50:48Z")

</div>

Yes, and as you move back and forth ot doesnt completely reset everything and collapse the apis you have expnaded haha

---

<div class="post-metadata">

**Author:** ![bkerryk](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/bkerryk/32/184126_2.png) [@bkerryk](https://forum.bubble.io/u/bkerryk)\
**Post date:** [November 28, 2024, 4:01am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/19 "2024-11-28T04:01:51Z")

</div>

Wow, yes please!

---

<div class="post-metadata">

**Author:** ![sem](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@sem](https://forum.bubble.io/u/sem)\
**Post date:** [November 28, 2024, 5:30am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/20 "2024-11-28T05:30:49Z")

</div>

Good point! You would think that it would be fairly easy to update the menu with a feature that we as users can put there what we want. For starters it could be a very simple checkbox next to a link or an editor page that shows qualifiying links that you can tab and end up on the ribbon. Possibly with dragging and dropping the order of icon links in the ribbon.

Such a strategy could lead to a structure with fly out most used workflow tabs for instance so you do not have to drill down completely all the time.

---

<div class="post-metadata">

**Author:** ![stephane\_hildbrand](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/stephane_hildbrand/32/209881_2.png) [@stephane\_hildbrand](https://forum.bubble.io/u/stephane_hildbrand)\
**Post date:** [November 28, 2024, 7:25am UTC](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960/21 "2024-11-28T07:25:53Z")

</div>

Nice tweak 👍

But an “exciting update” announcement is a bit exagerated

[Next page](https://forum.bubble.io/t/upcoming-changes-to-backend-workflow-location/349960.md?page=2)
