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.
I’m still a bit confused… how does a Manual workflow differ from a User interaction workflow? 
Good question!
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.
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.
I have a GBT and need to loop through the rows and set-value of a compute column into a basic column.
I want this to be a manual process (by an Admin for example) so is this an example of a “server-side” workflow?
Testing this now…ignore please.
Yes, this is a good “server-side” use case where you use a Trigger Workflow action and a workflow with a Manual trigger
Depending on your use case, you could have a user’s button press trigger a workflow that has a Loop step that sets column values from a computed column
Please tell me if there is a queue for Workflows Manual, what will happen if two people press the button at the same time?
You create two concurrent jobs. They can execute in parallel
Manual Workflow is amazing! Extremely helpful for adding roles to users from the front end of the app!
Curious about what would happen when you update someone’s role like that at the same time they are using the app. Would they need a refresh to see new permissions and row owner rows?
I bet manual workflows would make for an awesome YouTube tutorial 
Yup! It’s on my list!
No need for refresh (in my experience). They’ll see new permissions almost immediately.
Yeah, same.
When row owners are applied or removed (which is effectively what you’re doing when you change somebodies role), any active users will be affected almost immediately.
When I setup a Manual tigger and add one item, that item name isn’t shown when I go to use that item when filtering a loop. If I have two items, their names are shown, but one just says Trigger. I’d like that Trigger to still show the pop out menu even when there is only one item. Thanks!
It appears that when I’m using a manual trigger from another workflow, there is no option to set a value/item with the current date/time from the dropdown. The webhook action allows for this so I expected to see it in a trigger workflow set with a manual workflow.
Edit: I don’t have any use case to actually use it here because I can use it in the manual workflow itself. I am just noting the difference with trigger webhook. And now that I’ve though about it, of course after I posted, I cannot think of when I’d need it.
Tell me, will the ability to work with User specific columns be added?
Agreed!
