SleekFlow Product Requests

Currently, the Facebook Lead Ads integration only captures the page_id and lead_id. It does not expose the campaign_id or ad_id. Adding these fields is crucial for our marketing team so we can properly track attribution, measure ROI, and know exactly which campaign or specific ad creative generated each lead directly inside SleekFlow. Reference: https://developers.facebook.com/documentation/ads-commerce/marketing-api/reference/adgroup

Context & Use Case: I have a requirement to support a WhatsApp typing indicator. When my end-customer triggers a message, my custom LLM takes a few moments to process and generate a response. To keep the end-user engaged on WhatsApp during this delay, I want to display a live typing indicator on the user's personal WhatsApp interface. The Proposed Solution: You already have an internal endpoint (POST /conversation/typing) that triggers this behavior natively. Instead of building complex backend/UI overrides on my end, I propose exposing this existing internal API to clients. This would allow my custom LLM setup to independently ping the endpoint and trigger the typing state on WhatsApp while my AI generates the payload. This change does not impact our core platform UI and leverages infrastructure we already own. Thank you!

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.

Develop a native integration between SleekFlow and n8n to enable automations without manual API/Webhook setup, reducing technical complexity, accelerating onboarding, and expanding integration possibilities for customers using advanced workflows, AI, and process automation.

This feature enables users to process transactions and send payment links in United Arab Emirates Dirham (AED). Users benefit from the flexibility of supporting local currency for their customers in the UAE, providing a more seamless and localized payment experience.

API to fetch the online/offline status of teammates

For enterprise environments where staff use company-provided devices locked to a private intranet (no public internet or App Store/Google Play access), we need a supported method for app deployment and updates. We are looking for a standard technical workaround or deployment strategy, such as providing direct APKs for internal Mobile Device Management (MDM) systems to push updates, or specific whitelist requirements that IT teams can implement.

Develop a native integration between SleekFlow and RD Station to enable automations without manual API/Webhook setup, reducing technical complexity, accelerating onboarding, and expanding integration possibilities for customers using advanced workflows, AI, and process automation. RD Station is one of the most popular CRM and marketing automation platforms in Brazil. It is often regarded as the Brazilian equivalent of HubSpot, with a strong presence among small and mid-sized businesses and widespread adoption across the country.

Currently there are no Instagram as a channel for sendMessage API

When users click a Google Ad and land on a webpage before entering WhatsApp, the Google Click ID (GCLID) is lost the moment they enter the messaging channel. SleekFlow's current workaround, injecting a ref ID into the pre-filled WhatsApp message, fails in 80–90% of cases because users edit or delete the pre-filled text before sending. This makes it impossible to close the attribution loop between Google Ads spend and WhatsApp-generated leads natively within SleekFlow. Requested Capabilities GCLID / UTM parameter pass-through; a mechanism (e.g., a tracking script snippet, or a dedicated landing page widget) that captures gclid, gbraid, wbraid, and UTM parameters from the originating Google Ads click and associates them with the resulting WhatsApp conversation, independent of pre-filled message content. Native "Google Ads Click ID" contact property; a system contact property (gclid) that is auto-populated when a conversation originates from a tracked Google Ads click, analogous to how SleekFlow already surfaces utm_source / utm_medium or CTWA metadata for Meta Ads. Google Ads Offline Conversion Upload action in Flow Builder; a native Flow Builder action node (similar to the existing webhook action) that calls the Google Ads UploadClickConversions API when a conversion event occurs (e.g., contact label updated, lead status changed), sending the stored gclid + hashed phone number directly to Google Ads, without requiring a third-party middleware such as Make.com or n8n. Business Impact / Use Cases • Businesses running Google Search, Display, or Performance Max campaigns that drive leads into WhatsApp cannot measure campaign-level ROI (cost-per-lead by campaign / ad group / keyword) without this capability. • This is a known gap affecting customers across multiple regions (UAE, Brazil confirmed). The current workaround requires a custom server-side attribution database + middleware layer, which is infeasible for most customers without dedicated engineering resources. • Closing this gap would make SleekFlow competitive with dedicated CTWA attribution tools (e.g., WAct; https://www.waconversiontracking.com/ ) for Google Ads, not just Meta Ads.