Narek Zograbian My use case for this : user authentication with AI Agent. Let me explain : for authenticated dialog, AI Agent would require the user email. The user would provide his email, and the agent would add a task in a "users data" project if it does not already exist or it will create a new task for this user. The AI Agent would then store a authentication code (OTP code) in this task (custom field) and would send an email to the user with this OTP code. The user would then provide this code again to the AI Agent, the AI Agent would check if this code is linked to the user email in the "users data" project and if the otp code matchs the user, the AI Agent would be able to generate some content for this user (and could also store this content) in the "users data" project for this user (in a custom field of this user's task). That could be very powerful, kind of magic link to use AI Agent, but that requires that we can search for a task in a project (in my use case, the search would be against the email of the user)

chrishk This is interesting. It's almost like a source of truth for Taskade. How many rows of data would this encompass though?

Narek Zograbian one row per user, number of users : unknown, let's say 100

could be used only for otp code sending. so the number of rows could be very low in case a row is deleted once the user is "authenticated"

chrishk Thanks for clarifying!