Introduction to Actions

Create custom actions for your apps.

A useful way to think about apps is through the way users interact with them. Two very basic levels of interaction are viewing and editing data. But often, apps need to be able to perform actions.

For example, in this app, there is a Button which, when clicked, will take people to a website. This is because the button has the action Open Link.

An app with an Open Link action.

Opening a Form is another type of action. Open Link and Show Form Screen are examples of native Glide Actions. In other words, they trigger things that happen in your app. But you can also integrate third party Integrations like SlackOutlook, or OpenAI into Glide and trigger messages, emails, generated text, and much more.

The Action Editor

As you can see in the image above, it's possible to manually add actions to components. However, Glide also has an Action Editor that lets you save and reuse actions, or combine them into more complex workflows.

Complex workflows in the action editor.

In the right-hand panel of the Action Editor, you can review:

  • The data source for that action

  • Everywhere that action is used in the app

  • Run history for the action

  • Data sent when the action ran

  • Error message if the action did not run successfully

Have a question about Introduction to Actions? Ask the Glide community.

Updated more than a week ago
Was this article helpful?