Introducing Integrations: Connect GlideOS to 1,000+ tools

GlideOS
1

Your GlideOS apps can now connect directly to the tools your business already runs on — over 1,000 tools to be precise.

Tell Glide what you need in plain language, like pulling customer records from Salesforce or sending a Slack message when a row updates. Glide matches the request to the right service and builds the connection into your app.

Connect to integrations in two ways

From the project screen: select the plus sign next to Integrations, search for the service you need, and choose Connect.

Add GlideOS integrations from Projects
Add GlideOS integrations from Projects1175×940 53.1 KB

From chat: describe the task, and if your project doesn’t have that connection yet, GlideOS posts a card offering to set it up.

Add GlideOS integrations from Chat
Add GlideOS integrations from Chat776×582 75.5 KB

Every integration you connect shows up in the Integrations section of that project, marked Connected. Open it to refresh the connection or remove it.

Workflows & Integrations: A power-couple

These two features are strong on their own, but when paired together they are a force to be reckoned with. Workflows can now start from an integration event, or include integrations as part of workflow steps. Just chat with GlideOS to create workflows that use Integrations, or trigger off of them. It will walk you through the setup.

:bookmark_tabs: Read Documentation -or- :sparkles: Get Started

2

Are their specific data scale limitations in GlideOS?

Example, I am reading in 300 sheets with an average of 100 rows each (300 x 100) comparing these rows against a table with 200 rows in it (a region table). The App would support 100 regions that equals 3.0M+ rows. All regions would be separate from other regions (using row owners in the old system) so really only 30,000 rows + activity would be active for any given region.

Are these numbers that GlideOS is comfortable with given the current Glide limitations of 25K/app or BigTable constraints. Both number of tables read in (CVS/sheet/excel) as well as total row counts.

Specifically are their any other specific limitations/scale-out challenges when building with GlideOS especially with row count.

Also, I don’t see pricing based on row-count or storage size; is that documented somewhere?

Regards,

Matt