SleekFlow Product Requests

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.

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.

CONTEXT When we integrated to Shopify and created flow such as Order Confirmation, Abandoned Cart reminder, etc, we usually put the item name as one of the variable At the moment, item name variable is normalized_line_items However, normalized_line_items will return the SKU instead of the product display name This created an inconvenience and confusion as normally SKU is for backend staff, not the end customer. REQUEST Either setup a new variable in the Flow Builder to return the product name, or update the existing normalized_line_items variable instead.

Context: Currently, the Ticket retrieval data structure only returns internal database IDs for several key ticket attributes instead of their user-facing frontend names. This creates friction because developers have to perform extra manual testing to discover what each internal ID maps to, and it requires building and maintaining a custom mapping table just to display human-readable ticket details or map backend values for create/update operations. It would be highly beneficial if the returned Ticket payload included the corresponding frontend/human-readable values alongside the IDs. Currently, the only alternative is manually mapping these values or making separate configuration calls to fetch the ID-to-name metadata, which adds unnecessary overhead and latency to our integration. Thank you

Current Use Case: There is always a need for the client to synchronize messages from time to time via calling the API; however, the current process requires sequential API calls to retrieve information: Get Conversations https://api.sleekflow.io/api/conversation/all Get messages in conversation https://api.sleekflow.io/api/conversation/message/{conversationId} Get contact https://api.sleekflow.io/api/contact/{userProfileId} If the /api/conversation/message/search endpoint could support parameters for 'message start time' and 'message end time', and return conversation, message, and contact information in a single response, it would streamline the process of retrieving conversation messages via the API.

Background We are using Shopify, and need our store products to appear in the WhatsApp catalog. Currently, there is no direct sync between Shopify and WhatsApp catalog, so we must MANUALLY add or import products into FBBM. This creates significant operational overhead and makes catalog management inefficient. Request Enable product sync from Shopify to the WhatsApp catalog. Expected Outcome Product information and availability in the WhatsApp catalog should automatically reflect the latest published data in Shopify, to reduce manual work and keeping the catalog up to date.