Workflow automation behind every site.
Wire backend events together so forms, orders, bookings, campaigns, and support conversations can trigger the right follow-up automatically.
Best for
- order follow-up
- booking reminders
- lead routing
- admin alerts
Use it when client operations need to happen after the click: reminders, alerts, routing, enrichment, syncs, and recovery flows.
What this module gives your project.
Event triggers
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Scheduled triggers
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Webhook calls
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
API calls
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Execution logs
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Custom UX without rebuilding backend state.
- Webhook triggers
- Clear completion states
- Less custom glue code
- Auditable backend actions
A client-facing back office for the same module.
- Workflow builder
- Run history
- Failure visibility
- Schedules
- Action configuration
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.
- Choose the trigger
- Connect actions and branches
- Watch execution history while the client project runs
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.
POST /v1/workflowsPOST /v1/workflows/triggerGET /v1/workflows/{id}/runs