Forms that feed the backend.
Collect leads, support requests, onboarding details, and custom submissions directly into Arky, then route them through workflows and admin views.
Best for
- lead capture
- client intake
- quote requests
- support requests
Use it when forms need to become records, conversations, notifications, or workflows instead of inbox clutter.
What this module gives your project.
Dynamic fields
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Submissions
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Email templates
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Validation
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Workflow triggers
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Custom UX without rebuilding backend state.
- Form schema
- Validation feedback
- Submission endpoints
- Confirmation states
A client-facing back office for the same module.
- Submission inbox
- Field definitions
- Email templates
- Workflow routing
- Profile connection
Code the frontend. Connect Arky underneath.
Start with the frontend stack the project deserves, then connect only the Arky modules it needs. The admin, API, SDK, and backend workflows stay behind the custom experience.
- Create the form in admin
- Render it in the frontend
- Route each submission to the right follow-up
import { createArkyStore } from "arky-sdk/storefront-store";
const arky = createArkyStore({
baseUrl: "https://api.arky.io",
storeId: "your-store-id",
locale: "en",
});
await arky.setup({ hydrateCart: true });
// Use the module helpers your frontend needs.
// The client keeps full control over markup, routing, and UX.Useful integration touchpoints.
GET /v1/storefront/{storeId}/forms/{id}POST /v1/storefront/{storeId}/forms/{id}/submit