Monster model. I'm sure there are bigger ones

Got an agent created for something I’ve been putting off for 18 months. Now that it only takes a day or two to create, I decide it was worth the effort. Still have some outputting work to do, part of which is launching this into a simulation engine being worked on elsewhere.

There are actually 10 workflows. This is an “orchestrator”. I’m thinking about moving some of this off to workflows using jumps, but I’ll have to sleep on that one.

Question: Is there a good option - given the way we can implement these - for storing data for a particular user in a database? Ex: If I were to embed it, is that possible? I haven’t even looked into how it compartmentalizes stuff. But ultimately, I need longer term storage because this generator produces “value models” that we use as a foundation market prioritization using surveys (or simulations soon) and a “doc” or Notion isn’t going to cut it.

Hi @mikeboysen,

You can set up an external database like Supabase and connect it to your Agent using either a Custom Function or an HTTP Request block. That way, you can fetch and store user-specific data at both the beginning and end of your workflows.

1 Like