Apps & Integrations

An app connection lets a step act inside another service, using an account you have signed in to: it sends the Slack message, or adds the spreadsheet row. You sign in once, and every step that needs that service can use it.

Glow provides a broad catalogue of pre-built business app connections. The Integrations Directory  is the current list of available apps, triggers, and actions.

The Integrations Directory

To see what a given app can do before you build with it, search the Integrations Directory . It lists every trigger and action Glow supports for each service.

How to use the directory:

• Search any app: Type the name of the tool you use (e.g., Salesforce, Slack, Notion).
• View available actions: Click on any app to see the exact triggers and actions Glow supports out of the box for that specific tool.
• Request an app: If the app you need is not listed, submit a request from the search bar.

Using your own API keys

Most apps connect over OAuth, and Glow stores and refreshes those tokens for you.

Where a service authenticates with an API key instead, you supply your own key in the connection settings. That usage is billed to your account and covered by your own agreement with the provider. Keys are stored encrypted. See Credentials.

Glow’s AI steps are the exception: they run on managed infrastructure and need no key at all.

How apps work in Glow

When you drag an app onto the canvas, Glow provides two layers of functionality:

1. Authentication Handling: Glow securely stores your OAuth tokens, API keys, and passwords, handling token refreshes automatically.
2. Pre-built Actions: You get a clean UI with dropdowns and input fields specific to that app, rather than raw HTTP requests. Examples: “Send Slack Message”, “Update CRM Record”.

What’s Next?

• Sign in to your first app in Connecting an App.
• See what to do when an account stops working in Managing Connections.
• Call a service Glow has no integration for with the HTTP Request step.