Expanded Starting Nodes for Workflows/Chatflows to Enhance Automation Capabilities

[AndyMik90]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

I'm trying to build different workflows that many businesses can use (general workflows), but the limitation in many instances is the start node, which is basically just a query entry with options. Is there any plan from the team to develop a variety of starting nodes for workflows/chatflows in the near future?

Example starting nodes that would be useful:

• New Email: Trigger workflows based on incoming emails from email integrations like SMTP, Gmail, Azure, etc. This could be used for support ticket automation, order processing, and more.
• Incoming Calls: Integration with services like Twilio to handle incoming customer service calls with a voice-based chatbot. This can streamline customer support and provide immediate assistance.
• Update in Google Sheet: Trigger workflows when a row or column in a Google Sheet is updated. This can be used for real-time data processing, reporting, and notifications.
• RSS Feed: Automate workflows based on updates from RSS feeds. This can be used for news aggregation, content updates, and newsletters.
• Webhooks: Allow external applications to trigger workflows via webhooks. This can provide a high degree of flexibility and integration with various third-party services.
• Database Changes: Trigger workflows based on changes in a database (e.g., new record, updated record). This can be used for inventory management, CRM updates, and order tracking.
• Social Media Mentions: Trigger workflows based on mentions or messages on social media platforms like Twitter, Facebook, etc. This can be used for brand monitoring, customer engagement, and support.
• File Uploads: Trigger workflows when files are uploaded to cloud storage services like Google Drive, Dropbox, or OneDrive. This can be used for document management, content approval processes, and more.

2. Describe the feature you'd like to see

More starting nodes, or a robust system for creating starting nodes, much like the model/tool provider yaml/code we have today.

3. How will this feature improve your workflow or experience?

Create a lot of cutting edge workflows that will help a lot of businesses.

4. Additional context or comments

No response

5. Can you help us with this feature?

• I am interested in contributing to this feature.

[loganclark360]

simplest form in the beginning until like learn and then gradually step up and change settings to where he gets more challenging, but right now I just need to have it to work. I can understand what’s going on and I get in trouble for doing wrong thing. W. Logan Clark

…

On Sun, May 19, 2024 at 9:57 AM Andy ***@***.***> wrote: Self Checks - I have searched for existing issues search for existing issues <https://github.com/langgenius/dify/issues>, including closed ones. - I confirm that I am using English to submit this report (我已阅读并同意 Language Policy <#1542>). - Please do not modify this template :) and fill in all the required fields. 1. Is this request related to a challenge you're experiencing? I'm trying to build different workflows that many businesses can use (general workflows), but the limitation in many instances is the start node, which is basically just a query entry with options. Is there any plan from the team to develop a variety of starting nodes for workflows/chatflows in the near future? Example starting nodes that would be useful: - New Email: Trigger workflows based on incoming emails from email integrations like SMTP, Gmail, Azure, etc. This could be used for support ticket automation, order processing, and more. - Incoming Calls: Integration with services like Twilio to handle incoming customer service calls with a voice-based chatbot. This can streamline customer support and provide immediate assistance. - Update in Google Sheet: Trigger workflows when a row or column in a Google Sheet is updated. This can be used for real-time data processing, reporting, and notifications. - RSS Feed: Automate workflows based on updates from RSS feeds. This can be used for news aggregation, content updates, and newsletters. - Webhooks: Allow external applications to trigger workflows via webhooks. This can provide a high degree of flexibility and integration with various third-party services. - Database Changes: Trigger workflows based on changes in a database (e.g., new record, updated record). This can be used for inventory management, CRM updates, and order tracking. - Social Media Mentions: Trigger workflows based on mentions or messages on social media platforms like Twitter, Facebook, etc. This can be used for brand monitoring, customer engagement, and support. - File Uploads: Trigger workflows when files are uploaded to cloud storage services like Google Drive, Dropbox, or OneDrive. This can be used for document management, content approval processes, and more. 2. Describe the feature you'd like to see More starting nodes, or a robust system for creating starting nodes, much like the model/tool provider yaml/code we have today. 3. How will this feature improve your workflow or experience? Create a lot of cutting edge workflows that will help a lot of businesses. 4. Additional context or comments *No response* 5. Can you help us with this feature? - I am interested in contributing to this feature. — Reply to this email directly, view it on GitHub <#4514>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH6TQ25Z6VL7UTJAUHUGK43ZDDKX5AVCNFSM6AAAAABH6QJR6SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYDINRZGYZDGMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[devojony]

Is there any progress in this matter?