Kiket docsFor designers & PMs
The no-code path through Kiket — visual canvas, inline inspectors, zero syntax.
You want to model a real business process. You don't want to learn YAML, git, or what a webhook is. Kiket is designed for you to do the first without needing the rest.
Your starter path
Create a project from a template
Start in the app, click New project → From template, and pick the one closest to your process. The template ships a working workflow, a board, and basic issue types — you edit from there instead of starting blank.
Most useful templates for non-technical users: Kanban, Scrum, Marketing, Sales, Product, Support, Legal.
Customize on the canvas
Every template opens in the visual editor. You can:
- Drag states around, add new ones, delete ones you don't need.
- Click a transition to rename it.
- Click a state to open its inspector — SLAs, approvals, automations, required fields — all in plain-English form fields.
Wire in notifications
Settings → Integrations → Marketplace. One-click install Slack or Teams. Now on any state, the Automations inspector tab lets you say "on enter, post to #contracts" — no code.
Share a dashboard with stakeholders
Dashboards page → New dashboard. Drag in widgets (stat, line chart, SLA stoplight). If you need to share with an exec without giving them a seat, toggle Public sharing and set a password.
You never need to
- Touch YAML. The canvas writes it; you don't read it.
- Learn git. The app commits on save; you never clone, pull, or push.
- Install anything. Everything happens in the browser.
You'll occasionally want to
- Simulate — the top-right button on every workflow editor drops a dummy issue and walks it through your states. Lets you catch "wait, this transition isn't gated" bugs before real issues hit them.
- Invite an engineer — when you hit a ceiling (unusual predicate, custom webhook), pair with someone on the engineering side for 10 minutes. They can do it in YAML while you watch; the change shows up on your canvas immediately.