I am creating the AI Agent with n8n and there, the Credentials are managed, as well as other account specific data (e.g. I have a google calendar integration, where the calendar name would only work with my credentials, since only I have it.)
How should we handle such things when submitting the agent?
2 Likes
Great question Stefan!
When building your agent, you’ll have to think about how this will work on the Live Agent Studio where any number of users will be interacting with the agent.
This means that for user specific services like a calendar, you’ll have to think about how the user will authenticate with their Google account and you probably can’t rely on the credentials set in n8n since that is just for your account.
Not the easiest thing, but it’s important to build this kind of functionality into your agent if you want to allow others to use it!
Alternatively for the competition, you can just have it rely on a single calendar like you do now and we can set up a “free for all” calendar (when we host it for you) just for people to try out your agent on the platform for the competition voting period.
Hey @ColeMedin , can you explain a bit more on this “free for all” calendar? I did not quite get it
I think what he means is create a public calendar that can be accessed without any authentication. Sort of like a dummy calendar that can be used for testing only.
1 Like
Yes that is correct! Tagging you in case you missed it @harusama8121