Jawad IqbalSoftware Engineer
← All work

From a conversation to a real business action.

A published Custom GPT connected to ChatCLB through 21 focused API operations and personalized OAuth access.

MY ROLE
API & AI integration engineer
CONTEXT
Custom GPT integration project
CORE STACK
  • Custom GPTs
  • GPT Actions
  • OpenAPI 3.1.1
  • OAuth 2.0
CONVERSATION → ACTIONArchitecture overview
01Custom GPTConversation
02GPT ActionsOpenAPI contract
03ChatCLB APIBusiness authority
REQUEST & EXECUTION PIPELINEEnd-to-end execution
01User PromptCustom GPT Agent

Natural language intent parsing & parameter extraction

02GPT EngineOpenAPI 3.1.1 Contract

Action schema selection & input constraint validation

03OpenAI GatewayOAuth 2.0 Auth

User-scoped bearer token attachment via OIDC

04API LayerChatCLB Core Services

Authoritative backend execution & structured status response

OAuth provides personalized access. This is a conceptual request flow, not a complete security or deployment diagram.

The problem behind the product.

A conversational interface needs more than fluent answers to be useful. It needs a clear contract with the application, access tied to the right person, and deliberate handling of actions that change business data.

How the pieces come together.

01

A focused contract for each action

Designed 21 operations through an OpenAPI 3.1.1 Actions API. They cover business discovery, services and availability, appointments, messaging, reviews, favourites, live menus, and POS orders.

02

Personalized access through OAuth

Connected the published Custom GPT to ChatCLB with OAuth-based access, supporting workflows that depend on the signed-in user.

03

Confirmation-aware workflows

Designed the integration around user confirmation and an authoritative backend. The conversational layer works through the application API rather than becoming the source of business truth.

  • Custom GPTs
  • GPT Actions
  • OpenAPI 3.1.1
  • OAuth 2.0
  • OpenID Connect
  • REST APIs

Engineering tradeoffs.

Confirmation-Aware Mutating Operations

Structured critical operations (e.g. appointment booking, order placement) with explicit two-step user confirmation in OpenAPI schemas to eliminate accidental state mutation via model hallucination.

Granular OpenAPI 3.1.1 Operation Decomposition

Segmented 21 business capabilities into modular operation definitions with strict parameter schemas, minimizing prompt context tokens while ensuring deterministic model tool-calling accuracy.

What the work made possible.

  • Built and published a Custom GPT connected to the ChatCLB platform.
  • Defined 21 focused operations in an OpenAPI Actions contract.
  • Connected personalized OAuth access with confirmation-aware business workflows.

An integration with ChatCLB, presented separately to explain the API contract and conversational workflow design. It is not counted as an unrelated SaaS product.

Let’s make it
work beautifully.

A new product, a complex integration, or a system ready for its next chapter.

Discuss your project

jawadiqbal3344@gmail.comReplies within 24 hours · UTC +05:00LinkedIn