Context & Use Case

We are actively building automation workflows and deploying custom AI Agents within SleekFlow to handle customer inquiries. Our internal database, CRM, and inventory systems run entirely on a GraphQL infrastructure.

Currently, when we use the "HTTP Request" action in Flow Builder or try to connect a custom API tool to an AI Agent, the platform only natively supports standard REST configurations (GET/POST with flat JSON payloads).

The Problem (Pain Points)

Requirement for Custom Middleware: Because SleekFlow cannot natively send or process GraphQL queries and mutations, we are forced to build, host, and maintain a dedicated intermediary middleware server. This middleware exists solely to translate SleekFlow's REST requests into GraphQL, and then map our GraphQL responses back into flat REST JSON bodies.

Increased Engineering Overhead & Latency: This translation layer introduces an unnecessary single point of failure, extra infrastructure costs, and added latency to our real-time customer journeys.

The Proposed Solution

We request that SleekFlow adds native GraphQL support to the custom API/HTTP action modules in both Flow Builder and AI Agent integration settings.

Benefits

For Customers: Allows enterprise teams with modern tech stacks to seamlessly connect their internal data to SleekFlow’s automation and AI tools without building intermediate REST wrapper middleware.

For AI Efficiency: Drastically optimizes token usage and accuracy for AI Agents by restricting data retrieval to exact fields.