Ok so here is the dilema:
I need to alow users to set up rules for pasing incomming JSON data. What I struggle to decide is how to set up the UX for them to be able to do it as painless as possible.
This is for my webhok.com project where you get the ability to consume webhook JSON data and set rules that then trigger actions.
As you can imagine webhok JSON data can be quite big. So what would be the most intuitive way to design rules?
p.s. For example GitHub/Bitbucket JSON data. Based on the JSON received you want to trigger some CI pipelines for example. And you could set a finegrained rulles that certain CI/CD triggers only for specific tags in a git repo (I personally used this aproach to build docker containers)
Any feed back will be much appreciated! :)
I don't know if it is helpful but checkout https://pipedream.com/
They have similar feature (http/webhook API), they are open-source and they way they handle UI for JSON payload is pretty good.
I had a look, can take inspiration from this. Is simmilar to what I planed to do.
Are you an active user of pipedream? How did you find them?
I am not an active user, only used it once or twice in my previous company.
Took me 5min to build a custom workflow to trigger an API whenever user complete a google form so I am quite happy with the product. I think zapier/IFTTT were quite expensive so I was looking for an alternative. I managed to stay within free tier with Pipedream.
I would say there are two things you could do:
[1] https://jqlang.github.io/jq/
What I'm thinking right now is to just have a table with key/value pairs and a search box. So you can easily find the data you are looking for and then set simple rules like 'mustMatch | startsWith | endsWith | contains'.
After I get some traction and paid users I can see most frequent usecases and add templates for those scenarios. But in the start for paid users they could save rules as private templates too.
This comment was deleted 2 years ago.