# Glide API and Integrations: GlideOS vs Glide Classic Routes

> How Glide connects: GlideOS links 1,000+ services at 0.01 credits a call; the Glide Classic API needs Business, Big Tables, and spends updates per row.

_Source: https://professionalstoolkit.com/articles/glide-api-and-integrations — The Professional's Toolkit · updated November 2026_

---

Connecting an app built with Glide (glideapps.com) depends on which of its two products you are in. **GlideOS**, the current agent-built product, reaches more than 1,000 services through integrations the agent wires up from chat, with each integration call costing 0.01 credits [1]. The Glide API documented for developers belongs to **Glide Classic**, the original builder: it needs Glide Classic Business or Enterprise, works only on Big Tables and is still a public beta. Zapier and Make.com routes are Glide Classic features too, and their runs can spend updates. The two products share no accounts, data or integrations.


**0.01 credits** — What each GlideOS integration call costs, drawn from the organization's shared credit pool.



- **1,045** — Integrations in the GlideOS directory, as read in November 2026
- **Business** — Lowest Glide Classic plan with the Glide API and Call API
- **Pro** — Lowest GlideOS plan with MCP and database connection strings


## How GlideOS connects to other services

Nothing gets installed. You ask the Glide Agent for what you need (post new orders to a Slack channel, pull contacts from a CRM) or add a service from the project screen, then approve a one-click authorization. Glide's directory lists 1,045 integrations as read in November 2026. The plumbing runs on Composio, and Glide's docs say the agent never sees the stored credentials. Integrations launched in July 2026 and left beta in September 2026, so this layer is young. Some services cannot connect at all because they use a sign-in method Glide does not support.

Three rules shape the bill. Each integration call draws **0.01 credits** from the same organization-wide pool that pays for building and for AI inside your apps. Charges from the outside service are billed by that service, not by Glide. And a connection belongs to the project where it was made: it cannot be shared with a second project, so two projects that both talk to the same tool need two connections. Any member with edit access can add or remove one. When the monthly credits are gone, new AI requests stop until they reset or you buy extra credits, as the [Glide pricing guide](/articles/glide-pricing) explains.

Plan gates are short. GlideOS Free allows one integration; paid plans have no cap on the count, though Glide notes that some services need a specific plan. Premium integrations come with GlideOS Pro and enterprise integrations with GlideOS Enterprise. On its Enterprise page Glide names SQL Server, Salesforce, SharePoint and Microsoft Teams, and says apps can call any service with an API. The pricing page does not list which services count as premium.


> 💡 **One connection per project:** GlideOS integration connections cannot be shared between projects, so keep apps that use the same tools in one project when that fits your setup.




> ⚠ **Updates stop the pipes:** When a Glide Classic team hits its updates limit without unlimited updates on, Call API, Trigger Webhook and workflows stop running.

## Webhooks, secrets and database access in GlideOS

Most real integration work in GlideOS happens inside workflows. A workflow can start on a schedule, from a webhook (a POST request with an optional secret header), from a data trigger when a row is added, changed or deleted, from an integration event, from an app button or by hand. Data triggers arrived in October 2026 and fire only for changes made through Glide itself, not for tools writing straight to the database. Workflows can be built on any plan but run only on paid ones: one enabled workflow on GlideOS Basic, five on GlideOS Plus, no cap on Pro.

Workflow steps cost credits on a falling scale: 0.1 credits each for steps 1 to 100, 0.05 for steps 101 to 1,000, 0.02 for steps 1,001 to 5,000 and 0.01 for steps 5,001 to 10,000. Glide's own example puts a 500-step run at 30 credits. When the agent sets a schedule it states the runs and credits to expect each month. Treat that as a forecast and check the workflow page, which shows credits for the last 7 days and per run.

### Stripe, API keys and connection strings

Stripe gets specific handling. Since October 2026 a Stripe event can start a GlideOS workflow; the agent hands you a webhook URL to paste into the Stripe Dashboard. Apps that take payments from their own users run through Stripe Connect, and the GlideOS Terms let Glide charge a per-transaction fee whose amount is not published. For any other tool with an API, store its key as a project secret, read-only or read/write by the key's permission. On Enterprise, secrets can be scoped by role so builders never see them.

Going the other way, GlideOS Pro generates **Postgres-compatible connection strings**, read-only or read/write, so a BI tool or script can read the project database. The string is shown once. Close the dialog without copying it and you generate a new one. Pro is also where GlideOS keeps 24-hour data backups, worth knowing before you hand a read/write string to an outside script. Unlike a Glide Classic sync, nothing flows back into a Google Sheet: GlideOS copies a sheet into its own database and does not write back.

### Your own agent over MCP

GlideOS Pro and Enterprise also run a remote MCP server. Claude, Claude Code, Cursor, ChatGPT or any MCP client signs in with OAuth as a specific person and gets that person's permissions; only admins and editors can connect, and each connection belongs to one organization. Each action can be set to ask first, always approve or never ask. Building through MCP spends your AI provider's plan rather than Glide credits, but workflows, integrations and AI features inside the apps still draw credits. Glide says unexpected credit use through MCP is not refundable. The [GlideOS AI builder guide](/articles/glide-ai-app-builder) covers the agent side.


> ⚠ **A team-wide API token:** The Glide Classic API bearer token reaches every app and table in the team, so anyone holding it can read and change all of that data.


## The Glide API in Glide Classic

Glide API v2.0 is a REST API at api.glideapps.com with endpoints for tables, rows, stashing, jobs and uploads, first released in July 2024 and still labeled Public Beta [2]. It works only on **Big Tables**. Point it at a Google Sheet, an Excel file or Airtable and it returns an error. Authentication is a bearer token scoped to the whole team, with access to every app and table the team owns, so it deserves password-grade handling.

The gate is Glide Classic Business. Glide Classic Business costs $199 per month billed yearly or $249 per month billed monthly and includes 5,000 updates a month; the Glide Bulk API sits on Enterprise. Below Business, Explorer and Maker teams get workflows and integrations but no Glide API and no Call API. The help article on the older API puts its Get Rows query on Business and Enterprise as well.

API traffic is metered in updates, even though edits made inside the app to Big Tables use none on self-serve plans. Adding, changing or deleting a row through the API uses 0.01 updates; reading a row uses 0.001. With stashing, which uploads large data sets in chunks of 500 to 1,000 rows, nothing is charged until the stash is committed. Creating and listing tables cost nothing. The older Glide Tables API is still documented, with up to 500 mutations per call, processed asynchronously and not guaranteed in order.

## Call API, webhooks, Zapier and Make.com in Glide Classic

**Call API** is the outbound half, also from Glide Classic Business. It sends GET, POST, PUT, PATCH or DELETE requests with headers, query strings and a JSON body, as an action or as a computed column [3]. Header and query values are marked secret automatically. As a column it refreshes every 30 days unless you set a shorter interval, and Glide's JSON integration parses what comes back.

Trigger Webhook is the cheaper exit. It needs a paid plan, uses one update per run, and needs only a URL and the values to send. One catch: it works only when someone is signed in, so a public app without sign-in cannot fire it. Inbound, a webhook-triggered workflow gets its own URL, accepts a JSON POST and supports a bearer token plus an Idempotency-Key header against duplicate events. That trigger is still beta, and Glide recommends Big Tables behind it.


> 💡 **Use stashing for big imports:** With the Glide Classic API, stashed uploads are charged only when committed, and a deleted stash uses no updates, so large loads can be tested first.


### Zapier and Make.com

Both connect to a Glide Classic app the same way. Your scenario or Zap can add, edit or delete a row and fetch one row or all rows, and the app pushes data out with Trigger Webhook [4]. Each Make.com action needs its own scenario. The link uses the Team API key, which only team admins can see. Glide sets no cap on scenarios or Zaps, but runs can generate updates. The old Trigger Zap action was deprecated in December 2023; use Trigger Webhook instead.

### What native integrations cost in updates

Since May 2023 every successful integration run in Glide Classic counts against the team's updates, while failed runs and results cached for 30 days do not. An OpenAI prompt run on 1,000 rows uses 1,000 updates, by Glide's own example. AI providers such as OpenAI, Claude and Gemini run on your own API key and bill you separately. HubSpot actions run on demand and do not sync. QuickBooks, Salesforce, Xero and the JavaScript Code integration are paid Enterprise add-ons.

Updates come at 250 a month on Explorer, 500 on Maker and 5,000 on Business. At the limit, Call API and Trigger Webhook stop running and workflows halt unless the team turns on unlimited updates. With it on, each update over the quota costs 2¢; by our arithmetic, 1,000 extra updates come to $20 and 5,000 to $100. The [Glide pricing guide](/articles/glide-pricing) covers the rest of the bill, and the [data sources guide](/articles/glide-google-sheets-and-data) explains which tables the API can reach.

## Which plan unlocks which connection

| Connection | GlideOS | Glide Classic |
|---|---|---|
| Native integrations | Free: one; paid: no cap | From Explorer (Free limited) |
| Premium or enterprise integrations | Pro / Enterprise | Enterprise paid add-ons |
| Inbound webhook trigger | Paid plans (workflows run) | Paid plans, beta |
| Programmatic access to app data | Postgres-compatible connection strings on Pro | Glide API (REST, beta) on Business, Big Tables only |
| Outbound HTTP calls | Agent-built workflows, project secrets | Call API on Business |
| Bring your own agent (MCP) | Pro and Enterprise | Not documented |
| Unit each run spends | Credits | Updates |

GlideOS Pro is the first GlideOS plan with MCP, connection strings and premium integrations; it costs $125 per month for 5 team members with 500 credits, billed monthly only, since Glide says annual plans are coming soon. Nothing carries across: an integration set up in Glide Classic does not move to GlideOS, because Glide has no tool to migrate apps between the two.


## FAQ

**Do Glide Classic integrations carry over to GlideOS?**

No. Glide says GlideOS and Glide Classic live in separate accounts that cannot share data, so every integration is set up again in a GlideOS project.

**Who can see what integrations cost in GlideOS?**

Only owners can open the GlideOS Usage page, which breaks credit use down by user, project, mode, workflows and integrations; Enterprise also sees a per-model breakdown.

**Does Glide Classic show when a Stripe invoice is paid?**

Not automatically. The Glide Classic Stripe integration sends invoices, and Glide's docs suggest updating the paid status through Zapier or Make.com.

**Can I connect more than one Slack workspace in Glide Classic?**

Each Glide Classic app connects to one Slack workspace, but different apps in the same team can connect to different workspaces.


## The bottom line

For a developer who wants a classic REST API over app data, Glide Classic Business with Big Tables is the documented route, beta label and per-row update costs included. Teams that mostly need their app to talk to other tools will find GlideOS simpler: the agent connects services, webhooks feed workflows and every call is metered in credits. Pick the product first. The integration options follow from it.



## Sources

[1] Glide docs: Integrations — https://www.glideapps.com/docs/os/integrations (2026-11)
[2] Glide API v2.0 — https://apidocs.glideapps.com/api-reference/v2/general/introduction (2026-11)
[3] Glide docs: Call API — https://www.glideapps.com/docs/automation/integrations/call-api (2026-11)
[4] Glide docs: Make — https://www.glideapps.com/docs/automation/integrations/make (2026-11)
[5] Glide pricing page (GlideOS) — https://www.glideapps.com/pricing
[6] Glide Classic pricing page — https://www.glideapps.com/classic/pricing
[7] Glide Terms of Service — https://www.glideapps.com/legal/glide-os/terms