Glide Integration Hub

Glide is the real estate transaction management platform used by RERI transaction coordinators (TCs) and agents. It manages the full TC lifecycle: create transaction, assign checklist tasks, upload documents, e-signature routing (DocuSign integration), and party management. Current integration uses browser automation (scripts/glide-automation.js) via Aurora session — REST API key has not yet been obtained. Read this hub before any TC automation, Glide webhook, or transaction-lifecycle integration work.

Quick reference

Field	Value
Vendor	Glide
URL	https://app.glide.us
KB doc	API
Auth method	API key (Bearer token)
Auth credential	op://Aurora/glide/api-key
Cred-proxy port	n/a (until NemoClaw B1-B6 ratified)
Webhook port	n/a (not yet wired — see Open Issues)
Webhook handler	n/a
Webhook dedup table	processed_webhook_events (24h TTL)
Tunnel path	n/a (register in FUNNEL-REGISTRY.md before adding)
Outbound API base	https://api.glide.com/v1
Sandbox base	https://api-sandbox.glide.us/v1
Rate limits	100 req/min (standard); 500 req/min (enterprise)
Rate-limit action	429 → wait X-RateLimit-Reset epoch seconds; Discord ops after 3 consecutive failures
Cost	$149/user/month(Standard);$249/user/month (Professional)
Backup/recovery	Glide-owned; no PITR; document exports manual
Discord alert channel	ops
Drift cadence	on-API-change
Status	production

⚠️ Open issue: TLS base URL

Documented in KB (2026-03-08): api.glide.us has a TLS certificate mismatch — cert is for *.glide.com, not *.glide.us. Use api.glide.com as the canonical base URL. All code, scripts, and env vars must reference https://api.glide.com/v1, NOT https://api.glide.us/v1. The Quick Reference table above uses api.glide.com/v1 (corrected). Verify this is still the case before any new integration build — Glide may fix the cert to match api.glide.us.

⚠️ API key status

As of 2026-03-08 KB note: No GLIDE_API_KEY exists in .credentials. Current integration uses browser automation (scripts/glide-automation.js). To obtain a REST API key: log into Glide → Settings → Integrations → Developer API → Generate API Key → store as op://Aurora/glide/api-key.

Components

• workspace/knowledge-base/glide/API.md — Full API reference: transactions, documents, tasks, parties, templates, timeline, webhooks, rate limits
• workspace/knowledge-base/glide/examples/ — Code examples directory
• workspace/scripts/glide-automation.js — Current browser automation fallback (Aurora session-based)
• _summary — TC coordinator agent; primary Glide consumer
• _summary — Deal reporting; reads Glide completion percentages

How it’s used

• Current: Browser automation via scripts/glide-automation.js — Aurora session logs in and drives Glide UI
• Planned: REST API integration (pending API key)
• Trigger: New HubSpot deal → betterfiles agent creates Glide transaction via POST /v1/transactions
• Workflow: Glide task.overdue webhook → notify TC via Discord betterfiles-build; Glide document.signed → update HubSpot deal stage to “Docs Signed”
• Agents involved: betterfiles (primary TC ops); atlas (deal completion monitoring)
• Failure mode: API key not present → fall back to browser automation; browser automation may break on Glide UI changes
• Success criteria: Transaction created with correct template; tasks_created: 47 (standard CA purchase); document.signed event fires and HubSpot deal stage updated

Key API patterns

Transaction lifecycle

POST /v1/transactions           — create (always apply a template)
GET  /v1/transactions?status=active
PATCH /v1/transactions/{id}     — update status, price, close_date
GET  /v1/transactions/{id}/tasks?status=overdue
POST /v1/transactions/{id}/documents/{docId}/send-for-signature
GET  /v1/transactions/{id}/timeline

Webhook events

Event	Action
transaction.created	Notify betterfiles-build
task.overdue	Alert TC in Discord
document.signed	Update HubSpot deal stage
transaction.status_changed	Sync to HubSpot

Template IDs (CA standard)

• tmpl_purchase_standard — Standard Purchase CA (52 tasks, 18 docs)
• tmpl_purchase_investor — Investor Purchase AS-IS (38 tasks, 14 docs)

Cross-links

Agents that touch this

• _summary — TC coordinator; creates and manages Glide transactions
• _summary — deal monitoring; reads transaction completion percentages

Skills that invoke this

• betterfiles-dispo-emails — TC email generation; Glide transaction status informs email content
• betterfiles-cda — CDA generation tied to Glide transaction close

Plans that govern this

• vendor-deep-audit-comprehensive-2026-05-02 — Glide included in vendor baseline
• openclaw-fragmentation-fix-2026-05-01 — TC automation layer in audit scope

Feedback rules

• feedback_no_plaintext_creds — API key must go in 1Password, never in .credentials plaintext
• feedback_live_over_memory — test against Glide sandbox before production; verify TLS base URL before coding
• feedback_probe_before_execute — curl auth test against GET /v1/me before wiring webhook handler

KB / source docs

• API — Glide REST API reference (last verified 2026-03-08)

System maps

• deal-lifecycle-map — Glide sits in the TC phase after HubSpot deal creation
• external-integrations — Glide as external TC platform node

Related: Credential layer cluster

All credentials stored in 1Password vault Aurora. See 1password for op:// CLI access pattern. Glide API key: op://Aurora/glide/api-key (pending generation from Glide UI). Webhook secret (HMAC-SHA256): op://Aurora/glide/webhook-secret (pending setup). The existing browser automation session credentials are Aurora-scoped and must NOT be stored in plaintext.

Related: Webhook/tunnel cluster

When Glide webhooks are wired, register handler in FUNNEL-REGISTRY.md first. HMAC-SHA256 verification required via X-Glide-Signature header. Handler must write to webhook_audit_log + processed_webhook_events for dedup. See cloudflare for tunnel governance and compliance-gates for webhook security pattern.

Related: Mobile app data layer cluster

• supabase — Supabase stores RERI website property data; Glide transaction data may be mirrored for reporting
• hubspot — HubSpot deal stage syncs from Glide events (document.signed → deal stage update); bidirectional link

Open issues / TODOs

• P0: Obtain Glide REST API key — log in → Settings → Integrations → Developer API → Generate → store as op://Aurora/glide/api-key
• TLS note: Always use api.glide.com/v1 (not api.glide.us/v1) — TLS cert mismatch documented 2026-03-08. Verify cert status before integration build.
• Wire Glide webhook handler: task.overdue → Discord betterfiles-build; document.signed → HubSpot deal stage update
• Register webhook endpoint in FUNNEL-REGISTRY.md before exposing via Tailscale Funnel
• Replace scripts/glide-automation.js browser automation with REST API calls once API key is obtained
• Confirm which plan template IDs (tmpl_purchase_standard, tmpl_purchase_investor) are active in production Glide account

Recent activity

• 2026-05-04: hub created (W3-S5, Wave 3) — TLS issue + API key gap flagged in Open Issues
• 2026-03-08: API.md verified (base URL corrected to api.glide.com; API key not yet obtained)