Expand the power of Glide Workflows with the Slack trigger, Manual trigger, and Human-in-the-Loop features
• Trigger workflows with Slack messages
• Trigger workflows that can use loops, nested conditions, and computed steps from a button and pass inputs
• Ask a human to give an input before finishing a workflow
Please share feedback in this thread
As a reminder, Preview features should not be used in Production apps. Read more about Glide’s product release cycle in our Glide Doc.
We now have two different types of workflows and two different workflow editors: “client-side” and “server-side” workflows.
Workflows triggered by App interaction are “client-side” workflows (or workflows that are triggered by the user’s device and processed on the user’s device). They use the legacy Workflow Editor.
Workflows triggered by any other trigger (e.g., Schedule, Webhook, Email, Slack, or Manual) are “server-side” workflows. That means they process in the background but not on the user’s device. They have access to the new Workflows Editor, which has new features like Loops, Computed steps, and nested conditional branches.
Use Cases
App interaction workflows are best when you want an action to process immediately and change a user’s experience. They are also essential for setting values in user-specific columns. For example, you might use this to show or hide a component.
Workflows with a Manual trigger are best for complex actions requiring many steps, processing data, or communicating with other tools and services. For example, you might want to use this for actions when a user’s button click leads to sending data to the QuickBooks API, which then creates multiple rows based on the API response.
