# All experience endpoints need a workflow?

**URL:** <https://forums.losant.com/t/all-experience-endpoints-need-a-workflow/891>\
**Category:** Help\
**Created:** [April 30, 2018, 12:19am UTC](https://forums.losant.com/t/all-experience-endpoints-need-a-workflow/891 "2018-04-30T00:19:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [April 30, 2018, 12:19am UTC](https://forums.losant.com/t/all-experience-endpoints-need-a-workflow/891/1 "2018-04-30T00:19:51Z")

</div>

I’m building a multipage experience using the navigation bootstrap. The page tabs will be used to render different Dashboard pages. I gather I cannot simply reference the endpoint URL of a dashboard page? I need to trigger a workflow and a response node to render the various pages from the navbar, is that correct? Anyone have any examples of this?

Thx

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [April 30, 2018, 3:05pm UTC](https://forums.losant.com/t/all-experience-endpoints-need-a-workflow/891/2 "2018-04-30T15:05:14Z")

</div>

Yes, every [experience endpoint](https://docs.losant.com/experiences/endpoints/) requires an [Experience Endpoint Trigger](https://docs.losant.com/workflows/triggers/endpoint/) that ultimately connects to an [Experience Endpoint Reply Node](https://docs.losant.com/workflows/outputs/endpoint-reply/) to respond to the request. You may build separate [experience pages](https://docs.losant.com/experiences/views/#pages) for each request, or you could build conditional logic into a common page to display different information based on the request.

Bear in mind, each experience endpoint doesn’t necessarily require its own workflow to respond to a request. For organizational purposes (and for bootstrapping a new endpoint) we recommend one workflow per endpoint, but you can certainly handle mulitple requests / responses under one cloud workflow. You would just simply build those request / reply nodes on the same workflow stage as your other functionality.