We’ve just launched Process AI on Product Hunt and we’d love it if you could show us some support! Head over there and take a look, and please post a comment if you’ve enjoyed using Process Street or have any questions, we’d really appreciate it
Hi @kashish1
Love this direction. It’s been good to play with but not as useful as so far hoped. Perhaps you’re using ChatGPT 3.5? Not looking for a response here as I’ve already posted suggestions to feedback, but I’d love to see more general conversation about successes so far from the community!
Bryan
Hi @vinay , oooh that’s a good question. It’s been almost a year since I dove in, and I’ve not tried since. I did post q’s and ideas to support/feedback, and talked a bit with @Ellie about it. The main thing I remember is that 3.5 wasn’t that useful either for creating a workflow or anything else , and I was hoping for more current, albeit likely more expensive, version.
@kdesilva I know you tried to use it in a few creative use cases. Ideas here?
I was trying to cheat the system a little bit and make it do straight computer programming but since AI can make the same mistakes as a human, it wasn’t accurate 100% of the time. If there were some kind of constraint system built in, that would make it way more useful to me. Something like Midjourney’s creative freedom parameter.
My prompt was something like this:
If {{ form.field1 }} was true, then copy text from {{ form.result1 }}.
If {{ form.field2 }} was false, then copy text from {{ form.result2 }}.
This would then supposed to copy the correct variable into the AI result field. It worked correctly about 50% of the time. I ended up making a Power Automate flow that does it perfectly now.
That was just a super simple version of what I was attempting, but it didn’t seem to matter however I was prompting it. Trying it again with gpt4 yielded perfect results, but I have a feeling the variables in process street tripped it up a bit. I also made a mistake in the above code, in reality it was {{ form.field1 }} for both, not {{ form.field2 }} for that second If statement.