Workflows & connectivity

Wire Kera into your ecosystem.

Configure workflows as state machines, and connect inbound and outbound webhooks — so a PR, a deploy, or any event flows in and out automatically.

Workflows

Your process. Codified.

Define states, transitions, and automated actions.
Connect to anything via webhooks.

Discovery
In Spec
To Do
In ProgressWIP 3
In Review
Ready for Deploy
Waiting for QA
From any state
Done
Frozen
Closed
✎ Description
✎ Priority
✓ Assignee
← PR merged
⚙ Test suite
✓ QA pass
↗ Deploy ✓
⏱ Close tasks
KERA-42Feature
KERA-58Bug
KERA-71Task

Connect to anything

Trigger CI pipelines, notify Slack, sync with external tools. Every transition can fire webhooks with full ticket context.

  • CI/CD pipelines
  • Slack/Teams notifications
  • External issue trackers
  • Custom automation

React to anything

GitHub, GitLab, and custom webhooks flow into Kera. Link PRs to tickets, auto-transition on merge, sync status from external systems.

  • GitHub PR events
  • GitLab pipeline status
  • Custom webhook sources
  • Auto-transitions on external events
Automate on transition

Every transition can trigger an action.

Simple enough for a productivity team, powerful enough for an AI-led one. Wire actions to state changes — no glue code.

Fire a webhook

Signed outbound events to any endpoint when a ticket moves.

Change state

Auto-advance or gate a ticket based on conditions.

Call a model

Trigger a model call with full MCP access — let an agent decide and act.

Notify

Post to a channel, assign a group, or ping a watcher.

A transition action, configured

on: transition PROD-* → in_review do: - webhook: https://ci.acme.eu/hooks/kera # signed, verified - assign_group: qa - call_model: # full MCP access prompt: "Summarize the change and flag any risks." scope: project:PROD # bounded by your rules

In and out

Outbound webhooks

Signed events to your endpoints on any ticket, doc, or workflow change.

Inbound webhooks

Receive events from your tools and turn them into work in Kera.

GitHub & GitLab

A PR raised or merged updates the linked ticket automatically.

Signed & verified

Every payload is signed; unverified webhooks are rejected, never silently accepted.

A GitHub PR, wired to a ticket

# Inbound: GitHub → Kera on: pull_request.opened match: head branch → KERA-<n> do: - comment: "PR #482 opened by @alex" - transition: in_review # Outbound: Kera → your stack (signed) on: ticket.transition POST https://acme.eu/hooks/kera X-Kera-Signature: sha256=…

Start building today. Your call.

Set up in under a minute. No credit card. Plain text you can export anytime. Bring your own LLM, or skip AI entirely.

Get started free