Integrations

Beta

Every plan can connect integrations. The Free plan is limited to one, and paid plans have no limit. Some services need a specific plan. The list marks those with the plan they need, and GlideOS prompts you to upgrade when you pick one.

Integrations connect a project to a service you already use. Each service brings its own set of actions, and GlideOS draws on them as it builds and runs processes for you.

Connecting an Integration

There are two ways to connect an integration to your project.

From the project screen

1

Select the sign beside Integrations.

2

Search for the service you want, or scroll the list. Each entry names the service’s category and how many actions it offers.

3

Open the service. Its panel describes what that service does.

4

Choose Connect. Most services hand you to their own sign-in and authorization screen.

  • Some services ask for credentials instead of a sign-in. A panel will open and show a field for each credential, and Connect stays unavailable until every field is filled. Select the beside a field to see what that service expects.

A few services can’t be connected at all. Their panel says so in place of the Connect button, because they use a sign-in method Glide doesn’t support.

GlideOS stores the credentials the service returns, and the agent never sees them.

From a chat

You can also connect to an integration from the chat. Describe a task that needs an outside service, and when the project has no connection for it, GlideOS posts a card in the chat naming the service it needs. From there you can Connect or Dismiss the suggestions.

Managing Integrations

The Integrations section on the project screen lists each connected service and marks it Connected. Selecting one opens its configuration panel, where you can Refresh or Remove that integration.

Starting a Workflow With an Integration

Workflows can be triggered by integrations. To set this up, tell GlideOS which event in which service should start the workflow. Glide will guide you through configuring the workflow from there.

What Integrations Cost

Integration use draws on the same credits as the rest of GlideOS. Each call an integration makes costs 0.01 credits.

The Usage dashboard displays a breakdown of how integrations are using credits in your organization. It lists each integration the organization has used, the number of calls, and the credits those calls used, over a time range you choose.

Frequently Asked Questions

Composio is the service GlideOS uses to connect to integrations. It maintains the connection to each service and the set of actions available there. You can read more at composio.dev.

Connecting an integration to GlideOS doesn’t change your relationship with that service. Whatever plan you have, and whatever they charge for the use GlideOS makes of it, still applies and is still billed by the third-party service. GlideOS credits cover the integration call on Glide’s side only.

No. A connection belongs to the project you made it in. To use the same integration in another project, connect it there as well.

Any member with edit access can connect and remove an integration.