Tulip API to Query Apps & Step Names

[akbeta]

Would be excellent if it were possible to query an app by app ID and get step names and other useful information inside the app.

Looks like it was in development a while back but not sure if it ever was implemented.

Additions to the Tulip API, Export an Applications JSON and Import an APP

Would be nice to be able to export the json for a tulip app through the API. As well as being able to import an app.

[Austin]

This is a great suggestion! Tagging some friends that I think will agree

@ZAP @cpuzzo @QHullfish @pgabrys @jacob.brightmeyer @JesseAlbritton @Tim_Reblitz

[kevin.kononenko]

Hey Drew, what are you trying to accomplish with this API?

[akbeta]

@kevin.kononenko, the goal is to create a “table of contents” for an app which can be updated as a tulip table easily without having to cycle through every step manually to generate the records.

This also unlocks a few other opportunities like knowing what the previous step name is, page numbers, etc.

I made an automated step-through which crested the records, but it’s clunky compared to what we could do with a simple API call.

This person was trying to do the same:

Get list of steps in app

I’m looking for a way to get the full list of steps in an app. The closest thing I’ve found is Display list of step of an App in the app like table of contents, but this seems a bit clunky. My use-case is that our app starts off by allowing users to select a process they will be working on. The list of processes is dynamic, and configured by our operations team, and propagated in Tulip via a connector. We try to match the name of the the process to the name of a step in the app, and eventually …

[kevin.kononenko]

Got it. Last question- does this need to be an API, or would it also solve the problem if the Player simply allowed you to choose a step with a table of contents that appeared by default for the app?

[akbeta]

Hi @kevin.kononenko ,

Thanks for continuing to follow up on this.

The ability to query Apps and their subsequent steps and group names directly would unlock more than just a table of contents, including wide-scale testing, app-level feature rollout verifications, improved navigation functionality, dynamic page numbering, and more. In addition, the table of contents we’re looking to create isn’t something that could just be a default option, as it’s dependent (in our case) upon group names and more.

Drew
Beta Technologies

[akbeta]

@kevin.kononenko,

Maybe a “safer” approach if an API isn’t ready to be public-facing would be the ability to access the App and Step ID’s directly in Tulip Expressions. This would allow us to create a table where the table record is AppID + " | " + StepID, and we would be guaranteed to know exactly which step, in which app, is being referenced. This would solve for issues with duplicate step names.

However, for the wide-scale testing and custom content we’re looking to create, an API would be extremely helpful.