-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flow and Forms #805
Comments
As I have a use case for this, I started looking into it (see my branch), this will require quite a lot of work:
|
me too! and i started a repo where i will try to create a flow from forms to deck. However, I am a bit unsure how to proceed:
is this a reasonable idea? |
Yes! Very much support this! I have an intake form for new clients. I would like to create a new user based on the information in the intake form. It would be a super simple flow:
|
this would be brilliant! There are multiple usecases coming to mind. Would it be possible to check a specific question and send e.g. talk messages to different accounts based on the answer maybe with the content of one or different answers of the same form? |
This comment was marked as off-topic.
This comment was marked as off-topic.
What is the current status on this? I would like to contribute to this issue and would like to know what I can do, for example: should I work off the branch @susnux created or is that one a "dead end"? If so, what progress has already been made? |
reading the issues #790 and #789, I thought that it would be interesting to make a further step and integrate Forms with Flow.
There are a lot of possible conditions and actions that could be of interest, like for example:
and so on...
An hypothesis of schema
conditions
actions
I put only the actions specific to the Forms app, it is clear that all the other actions would be usable.
The text was updated successfully, but these errors were encountered: