Siteglide

Connect AI agents to Siteglide, a digital experience platform agencies use to build sites, portals, and stores. Agents manage pages, module and WebApp items, users, categories, products, and form cases, and read orders so site content and CRM records stay in sync.

Verified 30 actions API key available

Siteglide website ↗ Platform Documentation ↗ Capability data verified 2026-08-10

A schedule or a content approval elsewhere opens the run, because the Siteglide Site API exposes no webhook subscriptions and this connector ships no triggers

The approved records are pulled from wherever the agency drafts them, one row per module item with its core fields and its values

List Module Items returns what already exists on the target site, so the run splits cleanly into creates and updates

Every custom field key in the payload is checked against the stored field map for this specific site, because a key such as module_field_3_1 means something different on every site

Create Module Item and Update Module Item write the rows, with core fields alongside the mapped custom fields

The created and updated items go to the account manager with the client site named and the field map version recorded

A run against a site whose field map has not been confirmed stops here, and the agency lead approves the mapping before anything is written

What This Integration Enables

Siteglide is an agency platform, and almost everything distinctive about this connector follows from that. An agency does not run one site, it runs thirty, and the API is shaped for it: every request carries a site URL, an API key, and a numeric site ID, so a single flow can be pointed at whichever client it is serving. The surface is correspondingly broad. CMS Modules and WebApps cover structured content and custom databases. CRM Users and Form Cases cover the people and their submissions. Categories, Pages, Products, and Orders cover the rest of a site that also sells things. List endpoints return up to 500 items per page, which makes a full sync a realistic operation rather than a pagination project.

Two properties are worth understanding before building anything. The first is that Pages here are a developer-grade surface, not a page builder: Create Page requires a unique physical file path and a metadata object, and optionally takes Liquid content, a layout, a format, and a searchable flag. Update Page merges provided metadata with existing metadata by default rather than replacing it. That is real power, and it means an agent writing pages is writing into the same space the agency's own developers work in.

The second is that custom fields are site specific. Module, WebApp, CRM, and product custom fields are passed through a Custom Fields object keyed by API field names such as module_field_3_1, webapp_field_1_1, cfs_field_1_1, or module_field_14/product/price/usd/1. Those keys are positional to how the site was built. The same key holds a price on one client site and a subtitle on another, and this connector exposes no schema call to check against. A field map is therefore not documentation, it is a runtime dependency, and the workflow above treats it as one.

The third thing to notice is what is absent. There is no delete on this connector at all: no delete for a module item, a WebApp item, a user, a category, a page, or a product. Everything an agent creates here it creates for good, as far as this API is concerned, and removal is a human in the Siteglide admin.

Without FlowRunner

Client content updated site by site The same change is applied by hand in each client's admin, in whatever order somebody got to them

Field mappings live in someone's head Which numbered field key holds price on which client site is remembered rather than recorded

Portal access granted ad hoc Secure zone assignments happen in the admin with no record of who asked or who approved

With FlowRunner

One run writes to the client site Creates and updates are split from a single set of approved records, with the site named on every write

Field mappings are checked before the write A run against an unconfirmed map stops instead of writing a value into the wrong field

Portal access is provisioned with a record Create User and Update User run inside a flow that captures who requested access and who approved it

Use Case Scenarios

One content set, many client sites

An agency maintains a shared body of content, such as compliance notices, service descriptions, or a legal template set, that appears across a portfolio of client sites. The master copy lives in Airtable, where the agency approves changes. The rollout flow runs per site: it loads that site's field map, calls List Module Items to see what already exists there, and splits the approved set into Create Module Item and Update Module Item calls. Where the field map for a site has not been confirmed since the last structural change, the run halts on that site alone and continues with the rest, so one unverified client does not block the portfolio and does not get written into blindly either.

Portal accounts provisioned from the system that grants them

A client's member portal runs on Siteglide secure zones. When a new employee is approved for access in the client's own system of record, the agent calls Get User by email to check whether the person already exists, then Create User with their name, email, and the secure zones their role grants, or Update User to widen an existing account. Custom CRM fields carry the client's own attributes such as department and account number, keyed by that site's field map. Every provisioning event lands in Slack with the requester, the zones granted, and the approving name, which turns portal access into something with an audit trail instead of a favor somebody did in an admin panel.

Client reporting that does not require a login

Account managers need to answer questions about client sites without opening thirty admin panels. On a weekly run the agent walks each site: List Form Cases per form for what came in, List Orders and Get Order for what sold, List Orders by User to spot the accounts buying repeatedly, and List Users for how the CRM is growing. It writes the result into the agency's own reporting in Google Sheets and posts the exceptions, meaning the forms with no submissions this month and the orders sitting in an unexpected state, into the account team's channel as an automation exception list rather than a dashboard nobody checks.

Human-in-Loop Highlight

The gate here is not on a delete, because there is no delete. It is on the custom field map, and the reason is specific to how Siteglide is built. Update Module Item writes whatever value you send to whatever key you name. The keys are positional identifiers such as module_field_3_1, they differ per site, and this connector offers no call that returns the schema, so nothing in the flow can independently verify that the key it is about to write holds the field the agency thinks it does. A run with a map borrowed from a similar client succeeds completely: every call returns a success, no error is raised, and the client's live site now shows a price where a subtitle belongs, across every item the run touched, with no delete available to take any of it back.

So the flow refuses to write to a site whose map has not been confirmed for the current run, and asks the agency lead the only question that resolves it: "Rollout to Harborside Dental, site ID 4417, 62 module items in Module 8. Field map for this site was last confirmed on the 3rd of June, before their template rebuild. Mapping to be used: module_field_8_1 to Service Name, module_field_8_3 to Duration, module_field_8_5 to Price. Sample of the first row as it will be written is below. Siteglide's Site API has no delete, so items created here can only be removed in the admin. Confirm this mapping, or send a corrected one?" The agent has already assembled the payload, resolved the creates against the updates, and rendered a sample. What it will not do is guess at the meaning of a numbered key on somebody else's live site.

That is human-in-the-loop placed at the point where verification is actually impossible for the agent rather than merely inconvenient. Two neighboring actions deserve the same treatment for their own reasons. Create Page writes a new page at a physical file path on the client's live domain, and a path collision or a wrong layout is visible to the client's visitors immediately. Create User with secure zones grants access to a member portal, which is a permission decision rather than a content one, and belongs to whoever is accountable for who can see what on that client's site.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

30 actions

CMS Modules

List Module Items Returns a paginated list of items in a Custom Module for the given module ID, up to 500 per page with sorting. The read that establishes what already exists on a site, and the basis for splitting a rollout into creates and updates.
Get Module Item Retrieves all data about a single module item, including its custom field values. Used to read the current state of an item before overwriting any part of it.
Create Module Item Creates an item in a Custom Module with core fields plus module-specific custom fields keyed by their API field names. The custom field keys are site specific, so this call is only as correct as the field map behind it.
Update Module Item Updates an existing module item with the fields to change, custom fields passed as an object keyed by API field name. It writes whatever value you send to whatever key you name, with no schema check available to catch a mismatched map.

WebApps

List WebApp Items Returns a paginated list of items in a WebApp, which is Siteglide's custom database, up to 500 per page with sorting. Used to inventory the records a site holds outside its CMS modules.
Get WebApp Item Retrieves all data about a single WebApp item, including its custom field values. The detailed read behind any decision that depends on the current record.
Create WebApp Item Creates a WebApp item with core fields plus WebApp-specific custom fields keyed by their API field names. Used to push records from a system of record into a client's custom database.
Update WebApp Item Updates an existing WebApp item with the fields to change. Same field map dependency as the module equivalent, and the same absence of any call that would verify it.

CRM Users

List Users Returns a paginated overview of the CRM users on the site, up to 500 per page with sorting. The read behind portal audits and behind reporting on how a client's contact base is growing.
Get User Retrieves all data about a single CRM user, including custom field values, identified by numeric ID or by email address. The email lookup is what makes it usable as an identity check before any provisioning write.
Create User Creates a CRM user with name and email required, optionally setting a password, assigning secure zones, and supplying custom CRM fields. Secure zones make this a permission decision rather than a content one, because they determine what the person can reach in the portal.
Update User Updates an existing CRM user by numeric ID, with custom CRM fields passed keyed by their API field name. Used to widen or narrow portal access and to keep client attributes current from the system that owns them.

Forms

List Form Cases Returns a paginated list of submissions for a specific form ID, up to 500 per page with sorting. The read behind routing new enquiries and behind reporting on which forms are producing anything.
Get Form Case Retrieves all data about a single submission, including the submitted field values. Used when a flow needs what the visitor actually wrote rather than the fact that they wrote.
Create Form Case Creates a submission against a specific CRM user for a given form. Used to record an interaction that happened somewhere else, such as a phone enquiry, in the same place as the ones that came through the site.

eCommerce

List Products Returns a paginated list of the site's products, up to 500 per page with sorting. The read behind catalog synchronization and pricing audits.
Get Product Retrieves all data about a single product, including pricing, inventory, and category assignments. Used to confirm current state before a price or stock write.
Create Product Creates a product with a required name, and optionally a slug, weighting, category assignments, and product-specific fields such as pricing and inventory keyed by API field name. The pricing keys are among the most site-specific in the system, which makes the field map particularly load-bearing here.
Update Product Updates an existing product with the fields to change, pricing and inventory passed as custom fields keyed by their API field name. A mismatched key writes a price into a field nobody is watching, or a value into the price field nobody intended.
List Orders Returns a paginated overview of the site's orders, up to 500 per page with sorting. The read behind revenue reporting and behind reconciliation against the client's accounting system.
Get Order Retrieves all data about a single order, including line items, totals, and customer details. Used when a summary is not enough and the individual transaction has to be explained.
List Orders by User Returns every order placed by an individual CRM user. The read behind account history, repeat purchase analysis, and answering a client's question about a specific customer without a manual search.

Frequently Asked Questions

What can FlowRunner do with Siteglide?

FlowRunner agents can run List Module Items, Get Module Item, and Create Module Item in Siteglide, plus 27 more actions.

Does connecting Siteglide to FlowRunner require OAuth?

No. Siteglide connects to FlowRunner with an API key, no OAuth flow required.

Can Siteglide trigger a FlowRunner workflow automatically?

Siteglide doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Siteglide

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us