Introducing Flows

Moltin Co-Founder, Adam Sturrock, introduces Moltin Flows
 
 

Moltin Co-Founder, Adam Sturrock, introduces Moltin Flows explaining what Flows is, why we named Flows, Flows and what you can do with this extremely powerful and flexible feature. 

What is Flows?

Flows is essentially an EAV system. EAV stands for Entity Attribute Value. You can think of this as sort of a database, where the entity is the database table. The attribute is the database table column and the value is essentially the record of the row that sits inside that table where you store the actual information.

This essentially allows you to create a structured relation or data schema that sits inside of the Moltin API. So you can create new resources that you can then call upon and use or you could also extend core resources, like products, orders, customers to sort of tailor Moltin and the schema that we provide to your use case

Why is it called Flows?

EAV systems are incredibly flexible and we wanted a name that sort of highlighted that flexibility when we named the feature. It's also a standard way in which you can do custom data inside of Moltin, across the entire API. It's not ten different ways to do ten different types of extensions.

It's also a play on the name Moltin, like molten lava in that it's flexible, fluid and adaptable.

What can you do with Flows?

You can do a lot of things with Flows. You could look at extending the product schema to store maybe technical specifications for a machine product, and you want to show that to a customer.

You could store meta titles and descriptions for a SEO or you could even store unique identifiers, like an ibind code or a book, for example.

On the integration side, for say orders, you might want to store a tracking code or you need to store some information inside of the Moltin order that you need to handle that downstream fulfillment side that happens behind the scenes.

On the creation side you could maybe think of a wishlist and you want to relate that to products and sort of pull in that relational data. And also link maybe a wishlist to a customer, to allow them to access their wishlist and manage it.