Is there anyway to make a dynamic interactive guide with condition to only show relevant info?

[Taima Björklund]

Turning here after looking around and testing multiple apps but getting none-the-wiser.

I was hoping to make an interactive troubleshooting guide in Confluence, where you pick the issue and depending on what it shows you different information/next steps much like in a form with conditions or skip-logic.

This app does more or less exactly what I need: Interactive Troubleshooting | Atlassian Marketplace

Sadly it's no longer supported. Are there other alternatives about anyone knows of? 

[Joshua Brock _ Seibert Group_ GmbH]

Hi @Taima Björklund ... hope all is well!

You've put your finger on a real distinction: you need a tool that provides information conditionally, not one that collects it. Most form-type apps are built for the opposite direction, so you're right that they feel off for this use case.

And Tobias is on the right track mentioning AURA — let me add some specifics on how it could actually work for your scenario:

Option A — Tabs (no-code, works today): If your troubleshooting guide covers a defined set of issue categories, AURA's Tabs macro gives each category its own pane. Users click the tab that matches their situation and see only those steps, no scrolling through irrelevant content. It's not dynamically conditional in a form sense, but for a finite set of scenarios it's quick to build and clean to navigate.

Option B — HTML macro (true conditional logic): For real "pick your issue → see only those steps" branching, AURA includes an HTML macro that embeds custom HTML, CSS, and JavaScript directly inside a Confluence page. You can create buttons that show and hide specific content sections on click, building a lightweight decision tree entirely inside Confluence. It does require some comfort with basic HTML/JS, but nothing exotic, and it keeps everything inside your Confluence instance with no external dependency.

If you're open to a marketplace app, a few things AURA brings that are relevant here: 

• 20+ macros including Tabs, Step-by-Step, Expand, and HTML — all no-code and living right inside the Confluence editor
• HTML macro for full custom interactivity when native macros aren't enough (show/hide sections, button-driven navigation)
• Works on both Confluence Cloud and Data Center — one of the few formatting apps available on both platforms
• Live embeds for Figma, Miro, and Google Sheets if you need visual content inline within a guide section
• Trusted by Porsche, VW, Vinted, Samsung, and many more

You can find AURA on the Atlassian Marketplace: https://marketplace.atlassian.com/apps/1221974

And in totaly disclosure, I work at Seibert Group, the team behind the Aura Apps. Hope this helps and best of luck!


Joshua
Content Writer & US Representative
Agile Hive and Aura Apps (products of Seibert Group GmbH)

[Tomislav Tobijas]

Hi @Taima Björklund ,

As you realized, native features probably won't cover something like this. 

What you could try (I know some of my colleagues played around with these) is the following apps:

• Forms for Confluence (Surveys & Request Workflows) 
• ConfiForms - Data Forms & Workflows for Confluence 
• AURA Content Formatting Macros Tabs LaTeX HTML in Confluence 

Or you could also work with Refined and build the whole site from scratch. 

Note that I've only tested some of these apps for some particular requirements, so I can't say for sure what will work and what will not.

However, if you end up building a solution with one of these or anything else, it would be cool if you could share how you did it in the end 👀

Cheers,
Tobi

[Taima Björklund]

Hi Tobi, thank you for your answer.

I've tried Forms for Confluence - but run into the issue where I can't actually provide the user with information through it which makes it useless... Ideally the form would lead to a suggested solution, and there need to be space for a proper description beyond the "question", but it's built to gather information rather than give, as are most similar apps for forms I've found. Suppose my need here is a bit of a niché!

Will take a closer look at these and of course I'll share if I figure anything out. :)

/Taima

[Olha Yevdokymova_SaaSJet]

Hi @Taima Björklund 

this is a bit of a niche use case because most form apps are designed mainly to collect information, not to guide users through information step by step.

Native Confluence options like Expand, Tabs, or page trees can help structure a guide, but they usually won’t give you true “if the user selects X, show only Y” logic. So if you want something closer to a troubleshooting decision tree, you’ll likely need either a macro-based workaround or a form-style app that supports conditional content.

Another approach you might consider is Smart Forms for Jira, developed by my team. It’s not only for collecting requests — you can also build guided flows using:

• Conditional logic to show only relevant next steps based on the user’s previous answer.
• Content elements like headings, formatted text blocks, instructions, links, tables, and info panels.
• Embedded content for images, videos, or other visual guidance directly inside the form.
• External sharing or Confluence embedding, so the guide can be accessed from a Confluence page or shared as a link.
• Create Jira issue at the end, so if none of the suggested steps solve the problem, the user can submit a request directly from the same flow.

For example, your troubleshooting guide could work like this:

1. User selects the issue type: “Login problem,” “Access request,” “Performance issue,” etc.
2. Smart Forms shows only the relevant instructions for that issue.
3. The user answers another question, such as “Are you seeing an error message?”
4. Based on the response, the form displays the next troubleshooting step, a screenshot, a video, or a link to a Confluence article.
5. At the end, you can add: “Did this solve your issue?”
6. If they select “No,” the form can collect the missing details and create a Jira request for the support team.

Smart Forms supports conditional logic using a simple “When/Then” setup, where a selected value in a dropdown, checkbox, multi-choice, or radio button can show or hide specific fields/content. It also includes content blocks and embedded content, so the form can guide users with explanations, media, and instructions — not only questions.

So while it may not be a classic “interactive documentation” app, it can work well for a guided troubleshooting flow with a request submission fallback.