⭐ Making Steps Inputs/Outputs Human Friendly

why not a little toggle for us to see it in both YAML and JSON. YAML can be turned on by default.


Yeah a toggle, but also able set a default from settings.


Why do you need to customize this part as much? Isn’t the goal of the output to read and debug? Are there cases where the YAML format won’t do it for you on the UI?

Hi @ashrafsam,

Just send this to Abdul too, how should I read my errors from here? maybe there are some bug in teh display of the YAML, I am not sure btu this does not tell me much.

KR Bram

Now it’s getting interesting😂 @Abdul looks like there are more cases we have to cover in this conversion? Is that a stringified JSON or an actual JSON?

@Bram Do you have an answer or more info?

hi @ashrafsam mmm I think it’s HTML :wink: Abdul should have enough info for further testing I think, I’ve send him the data privately to work with. And we will share the outcome here.

Great, keep us posted!

As a notorious advocate for non-techy-friendliness this looks like a great change!
The YAML format tends to have some odd grammatical nuances that could confuse these people more than basic JSON, but I wouldn’t expect those to show up in plain API responses.

However, as mentioned/experienced by @Stockton and @Bram, this kind of “representation abstraction layer” can (and inevitably will) lead to issues.
If it’s indeed purely representational I’d strongly suggest adding a toggle to fallback to the “bare” JSON representation as @Karim_Yahia suggested. Technical users can then dive in if they need/want to.

Secondly, based on @Bram’s screenshot the YAML seems to be generated with 2-space indentation. I know that this is the recommended default for YAML, but for accessibility reasons this is incredibly hard to use for me and some of my colleagues. It’d be great if we could customize this, though I’d strongly recommend setting the default to 4 spaces to emphasize the “indented tree”-like nature to non-technical users, even for those without accessibility needs 2 spaces are fairly easy to miss.


I was thinking of a toggle to switch between formats, but I think that will just confuse no code users.
Your suggestion is correct, people can download/copy the YAML they see and use something like YAML to JSON Converter Online to convert their files.

1 Like

I don’t think it would, but if so, maybe the toggle could be hidden by default, and available in settings to enable?

1 Like

bring back JSON please

Can we have some form of option to have JSON? It’s easier for me to debug flows.

This is some decent bias towards JSON. Let’s talk more about it.

  • Did you notice that you can expand and collapse the items in the YAML format? This should help you explore the outputs easily.

  • Is the problem when you have neated JSONs inside the YAML format so it starts looking bad?

  • Is our implementation to YAML not perfect that makes you prefer JSON?

  • Or is it just that you prefer JSON?

We heard from users that JSON looked scary and that’s why we wanted to simplify it. So your elaboration will help us understand this better.

I’m pro-YAML, it’s definitely easier for non-technical users. However, I can also see why technical people might prefer the standard JSON they’re used to.

My main concern would be that most of the world uses JSON, so it can sometimes be easier to work with in combination with other tooling.

This kind of workflow gets very tedious very fast.

1 Like

Hello! Fantastic, they will make a tutorial for beginners like me hehe.

Hello! Fantastic, they will make a tutorial for beginners like me hehe.

I really don’t like this. 99% of API actions or integrations use JSON. Now when I’m creating a flow step by step each step outputs YAML which I can’t use anywhere and I have to do extra steps to convert YAML to JSON and cross the fingers the converter that I used didn’t add something extra…

JSON should be the default, you want to add YAML ? Great! Why not? But what is the benefit to remove JSON?

Hi @here,

Based on your feedback, we have decided to remove YAML and revert back to JSON.

We took the following steps:

  • YAML has been removed and changed to JSON.
  • Colors of JSON are no longer yellowish; they are now black and blue.
  • JSON is now expandable.

Next steps:
In the following weeks, we will improve our JSON viewer to be no-code friendly in a way that doesn’t change the format.

We always listen to the feedback, Keep it coming!


  • JSON is widely adopted in all software, which is natural to see the API response in that format.
  • Yaml could be a source of confusion in such case.

Array of Objects:

  - role: OWNER
    status: ACTIVE
    userId: 722ccb0b-90c0-4fd7-bfb9-fc2a7bc78914


  role: OWNER
  email: example@example.com
  status: ACTIVE
  userId: 722ccb0b-90c0-4fd7-bfb9-fc2a7bc78914

why is your password visible in the screenshot bro? @abuaboud


Thank you, Mo et al. :pray: