Have something to say?

Tell us how we could make the product more useful to you.

Full build web application tutorial series

I would really love to see a tutorial about a complete CRM-type web application build. You know, like the ones with the commonly seen left side panel, a user login page (with authentication), with toast notifications, tooltips, and popups, list data page, single details page, etc. I think with one complete build it would demonstrate how to build the different parts of a web application (each of which have their own quirks and nuances) and showcase Clutch’s capabilities. It doesn’t have to be one long video (although there’s nothing wrong with that too β€” and preferred in my opinion), but could also be a multi-video series. This way instead of learning about different topics in isolation, we’d get a good understanding (and also appreciation) of not only how to build all the β€˜Lego’ blocks, but also how to assemble and integrate them into a app. It’s day 1 of Clutch for me and I’m loving every minute of it. ❀️

Sean Bernardino 9 days ago

πŸŽ“

Docs/Training Request

Default Content-Type: application/json for REST and GraphQL Actions

Context: Users are attempting to send form data from Clutch to external services like Directus, which expect application/json payloads. However, Clutch's current default behavior sends the body as plain text unless the header is manually set. Problem: REST/GraphQL actions do not default to sending Content-Type: application/json, resulting in empty or invalid request bodies unless users manually set the header. This leads to confusion for users unfamiliar with header configuration, especially when trying to integrate with common services like Directus or WordPress. Current workaround: users must manually add the header via the action config. Proposed Solution: Default Content-Type: application/json if no header is set by the user. Allow header override: if a user explicitly defines Content-Type, respect their value. Consider exposing a dropdown UI for commonly used headers like Content-Type: application/json, Authorization, etc., to reduce manual setup and improve UX. Design Suggestions: UX reference: Strapi's GraphQL playground or Postman-style dropdowns. Could be part of the REST/GraphQL action panel or a reusable presets module.

Alex Prieu 10 days ago

πŸ’‘

Feature Request