Convex Workflow Design thoughts -
Ideating through a convert-kit style system and was inspecting the Workflow component.
Do you think this is a good choice for a convert-kit style automation system? Some of the questions I have -
- Can workflows be defined programatically? Meaning I setup a 'node-based' GUI on the frontend (react flow) and create a workflow from the graph of nodes
- What's a reasonable amount of concurrent workflows? A user in the system might have several automations that trigger off events in the system - such as a new 'client' getting added to the CRM.
- Are workflows supposed to be A-Z steps and then done? What about 'never ending workflows', or do you recommend scheduling a concrete workflow & managing the state (e.g., starting a new workflow based off an entry-event) outside of the workflow itself?
Thanks for the thoughts and advice here!
Do you think this is a good choice for a convert-kit style automation system? Some of the questions I have -
- Can workflows be defined programatically? Meaning I setup a 'node-based' GUI on the frontend (react flow) and create a workflow from the graph of nodes
- What's a reasonable amount of concurrent workflows? A user in the system might have several automations that trigger off events in the system - such as a new 'client' getting added to the CRM.
- Are workflows supposed to be A-Z steps and then done? What about 'never ending workflows', or do you recommend scheduling a concrete workflow & managing the state (e.g., starting a new workflow based off an entry-event) outside of the workflow itself?
Thanks for the thoughts and advice here!
