I've integrated OpenAI into Storyline, allowing you to input any tool you want to learn, and the course will be generated accordingly. While it's currently focused on tools, this capability is scalable to any content users want to learn.
Additionally, there's a question validation page where you can input your own questions, expected answers, and user responses, and then use AI to validate them. You can also edit tags by entering "Ctrl+ Q" on the last question page.
don't use OpenAI like in this example, the API key is stored in the storyline user.js* file - visible to all users who know the browser developer console
if the api key is misused, it can be expensive for the OpenAI account holder
NodeJS as shown by Chris Hodgson. And then use NodeJS on your server. Actually when you search for openAI API and Javascript you find most solutions based on NodeJS
Yes, I am very much aware that the key is visible in the console, along with the specific key, and I have also enabled the limit for the key, so it's fine. I just want this demo to be here so users can review it.
I am working on the server-side programming to hide the key, and I will update the demo once it's done.
@math - It would be really appreciated if you could delete the above screenshots. Thank you in advance.
12 Replies
This is very cool! Would love to know more about how you built it.
Thank you. We will connect sometime this week and discuss this.
I agree with Arron. That is very cool and would also love to know how you built it.
Likewise - would love to learn more - thanks in advance!
Hi Sinchu,
Can you share your .story file with us? TIA
don't use OpenAI like in this example, the API key is stored in the storyline user.js* file - visible to all users who know the browser developer console
if the api key is misused, it can be expensive for the OpenAI account holder
https://platform.openai.com/docs/guides/rate-limits/usage-tiers?context=tier-free
more infos:
https://help.openai.com/en/articles/5112595-best-practices-for-api-key-safety
* user.js = client-side enviroment (browser)
@Sinchu Raj: you should delete your example from Review 360 and/or modify it with an additional backend server
This post was removed by the author
Can you explain the process of incorporating OpenAI's ChatGPT into Storyline projects for course developers?
Since I saw the original post, I positioned it as a viable solution for one of my clients. Do you have an alternative then?
you need a second server
there is no alternative that I know of
NodeJS as shown by Chris Hodgson. And then use NodeJS on your server. Actually when you search for openAI API and Javascript you find most solutions based on NodeJS
This post was removed by the author
Hi Math Notermans, Jürgen Schoenemeyer,
Yes, I am very much aware that the key is visible in the console, along with the specific key, and I have also enabled the limit for the key, so it's fine. I just want this demo to be here so users can review it.
I am working on the server-side programming to hide the key, and I will update the demo once it's done.
@math - It would be really appreciated if you could delete the above screenshots. Thank you in advance.
you should really deactivate the example above and only activate it again once you have solved the problem with the publicly visible API-key.
anyone who knows the link above can easily use your Open AI API-key in another project, the costs incurred will be charged to YOUR credit card