VIZION AI
Back to Systems
Secure AI Integration System

API-Connected GPTs

Connecting an AI assistant to company data is easy. Making sure it cannot leak confidential records, overwrite live databases, or execute unvetted changes is where most implementations fail. We build zero-trust edge gateways that keep your data intact.

System Architecture & Flow

Vizion API-Connected GPT System Flow — Zero-Trust Architecture & Mandatory Attended Execution
Click to expand full diagram

Starting Baseline Setup & Maintenance

Starting at 10,000 CZK setup · 10,000 CZK / mo

(approx. €420 setup · €420 / mo baseline)

The setup fee covers designing the edge gateway, defining strict OpenAPI 3.1 action schemas, configuring bearer security and HMAC verification, and connecting a secure read or proposal workflow to your database or spreadsheets.

Live integrations break as APIs evolve. Monthly maintenance covers endpoint version updates, monitoring token usage and response latencies, security certificate and credential rotation, and continuous testing to ensure prompt changes never bypass data boundary rules.

Final scope depends on the number of connected endpoints, database write permissions, and user seats. We clarify the exact scope during discovery before any commitment.

See the Czechia Expat Job Scout, our public working proof demonstrating zero CV storage, HMAC request signing, and bounded discovery queues.

The Real Problem

Prompt rules are not a security perimeter. Instructing an LLM “do not edit column C” or “keep this confidential” is wishful thinking. Prompt injections, hallucinations, or naive user inputs easily bypass conversational guidelines.

The Semantic Stance

Enforce business operations at the gateway. The LLM is never granted generic primitives like updateCell, deleteRow, or executeQuery. It can only call bounded semantic verbs like searchRecords or submitDiscoveryProposal.

What It Proves

Zero-trust AI integrations can be built on lean, cost-effective serverless architecture—Cloudflare Workers, signed webhooks, and audit-logged spreadsheets—without paying for enterprise middleware or risking company data.

Why This Exists

Custom GPTs and AI assistants have become the default interface for internal team workflows: searching product notes, checking inventory, sorting lead emails, and finding company policies.

Most teams connect their data using off-the-shelf plugins or direct account links for Google Drive, Notion, and spreadsheets. Because the setup screen looks official, teams assume it is safe.

It isn’t. Off-the-shelf connectors grant the language model direct write permissions to your live files. When an employee asks the assistant in chat to “clean up outdated contacts” or “update customer rates,” the model executes raw write commands straight against your master rows. There is no intermediate staging, no pre-flight diff, and no safety gate. A single misunderstood column or an indirect prompt injection in a customer email can overwrite formulas with flat text, delete records, or apply edits to the wrong client.

Our API-Connected GPT system establishes a zero-trust perimeter between the AI model and your internal databases. Every request is verified by an edge gateway, validated against strict schemas, stripped of personal data, and authenticated with cryptographic signatures. The AI only ever performs the exact business tasks you allow.

The Reality

The trap of native chat connectors

Authorizing a standard Google Drive or spreadsheet plugin inside a chat tool gives an unpredictable model direct write access to your actual files. Prompt rules like “be careful not to delete formulas” offer zero perimeter defense.

The attended edge pattern

An AI should never hold direct database mutation credentials. Our edge gateway acts as an isolated holding tray—the assistant can only submit draft proposals to a staging queue, leaving company records physically protected until a person on duty clicks “Approve.”

Small-Business Application Scenarios

Four workflows where teams use this safely.

This architecture connects conversational assistants to everyday business tools while guaranteeing that the AI can only draft proposals—never execute irreversible database actions without human review.

Lead & Inquiry Intake

Sales, Agencies & Real Estate

An employee or customer pastes a messy email, call transcript, or web inquiry. The assistant checks your service catalog and drafts a structured lead record with company name, project scope, and urgency.

Enforced Hard Boundary

The AI cannot send emails, update pipeline deal stages, or alter existing client records. It only creates an intake proposal for human sales review.

Google SheetsNotionHubSpotAirtable

Customer Support Triage

E-Commerce, Services & Software

Reads incoming client questions, checks your knowledge base for approved answers, and creates a categorized ticket with urgency tags and affected office locations.

Enforced Hard Boundary

The AI cannot close tickets, issue refunds, change contracts, or view other customers’ private accounts. A duty manager reviews and assigns the ticket.

ZendeskFreshdeskEmail InboxesInternal SQL

Quote Request Preparation

Trades, Studios & Manufacturers

Compares customer project requirements against your pricing rules and inventory lead times to draft an itemized estimate with listed assumptions.

Enforced Hard Boundary

The AI cannot grant unapproved discounts, promise delivery dates, or issue a binding quote without owner sign-off. It only prepares the draft.

Google SheetsERP CatalogsCustom Databases

Internal Policy & Handbook Lookup

HR, Operations & Hospitality

Gives staff fast, conversational answers across employee handbooks, property check-in procedures, vendor agreements, and compliance guidelines.

Enforced Hard Boundary

Strictly read-only. The AI has zero write routes to alter company policies, disclose employee salary data, or leak access codes.

Google DriveNotionMarkdown Repositories

Challenging Our Own Claims

What we assumed, what we tested, and what actually broke.

Connecting an AI to a spreadsheet is easy in a demo video. Making sure it cannot corrupt master data, hallucinate parameters, or leak private records in production is where naive setups fail. Here are four real breakdowns from our test harness, and how we engineered defenses around them.

The Prompt Boundary Fallacy

Why conversational instructions are not a security firewall

What we assumedTelling an AI in system instructions “Do not edit column C” or “Keep client records confidential” would reliably protect company spreadsheets.
What actually happenedNormal user phrasing, unexpected accents, or indirect prompt injections easily bypassed conversational guidelines. If an AI holds write access, prompt rules alone cannot stop it from modifying live records.
What we changedWe removed database edit permissions from the AI entirely. Security is enforced on an independent edge server that physically blocks forbidden commands before they ever reach company files.

The Two-Tier Write Invariant

Why off-the-shelf spreadsheet connectors are an operational hazard

What we assumedUsing an off-the-shelf spreadsheet connector or asking an assistant to update rows directly in chat was fine as long as we told the prompt to confirm before writing.
What actually happenedOff-the-shelf connectors grant direct write access with zero safety layer. When chat models write directly to live cells, network timeouts trigger duplicate rows, formula cells get overwritten with static text, and subtle hallucinations apply changes to the wrong customer row without leaving an undo queue.
What we changedWe banned direct write access completely. The AI can only append a proposed draft to an isolated holding queue (Discovery_Queue) and log an audit row (Change_Log). Master company records remain physically untouched until a team member on duty clicks “Approve.”

The Idempotent Replay Trap

What happens when networks take 4 to 6 seconds to respond

What we assumedWhen an API call is made, the assistant waits for a response and moves on.
What actually happenedGoogle Sheets and internal webhooks sometimes take 4–6 seconds to respond. The chat interface timed out, assumed failure, and retried the request—silently creating ghost duplicate entries in the background.
What we changedEvery write request must carry a unique cryptographic token (an idempotency key and nonce). If a request retries, the server recognizes the token, blocks duplicate writes, and returns the original confirmed receipt.

Cryptographic Gateway Isolation

Why Bearer API keys alone leave internal backends exposed

What we assumedA standard password or Bearer token between the AI and our server was sufficient protection.
What actually happenedIf an internal endpoint is exposed publicly, anyone who intercepts or guesses the URL can send unauthorized commands directly to your spreadsheets.
What we changedThe edge gateway cryptographically signs every approved request using HMAC-SHA256. Your internal database checks the signature, timestamp, and payload hash—instantly discarding any call that didn’t pass through our security scanner.

Live Working Proof

Tested on the Czech job market.

We implemented this architecture for the Czechia Expat Job Scout: a custom GPT connected to a 50+ source database through a Cloudflare Worker gateway with zero CV storage and human-reviewed discovery proposals.

Verified Architecture

  • Custom GPT with OpenAPI 3.1 action specification
  • Cloudflare Worker edge gateway with HMAC-SHA256 signing
  • Append-only proposal queue with full audit log
  • Zero PII/CV retention and GDPR compliance policy
View the Job Scout overview