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! 🙂
2 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
My biggest concern is that it doesn't appear I could define a workflow programmatically