DEV Community

Mehmet Burak Akgün
Mehmet Burak Akgün

Posted on AI-assisted

A team interface for AI workflows: pages, Kanban and MCP

You build a contract review workflow. It runs successfully and returns the results you expected.

Then the rest of the team needs to use it.

Where do they run it? Which documents still need attention? Who owns the next step? Where should someone leave a comment?

Those questions shape the interface around an automation. They’re also what we’ve been working on with Heym Work.

Heym Core is our self-hosted AI agent platform. Heym Work gives teams an interface for using the workflows running underneath it, with pages, task boards and chat.

Ceren recently recorded two walkthroughs using a demo legal team. Here’s what they cover and the thinking behind them.

Part 1: A place to run workflows and see what needs attention

The first video covers Home and Pages.

Overview brings together the workflows the team already has, reports and pinned widgets. People can run a workflow and check the information they need from the same screen.

World provides another way to navigate the workspace. In the legal demo, areas include Contract Inbox, Knowledge, Risk Review and Approval Desk. The names, content and click actions can be configured around the team’s work.

Pages let you bring the relevant information together for a particular job. In the demo, that includes client details, document status, owners, next actions and workload.

One example is a “Needs Attention” table. Ceren describes what she wants through Edit with AI, and Heym builds the widget on the page.

That’s the part I find useful about this approach: the team can ask for a view that matches the question they’re trying to answer.

Watch Part 1: Pages and Overview, about 5 minutes

Part 2: Keeping track of the work around an automation

The second video follows tasks through a shared Kanban board.

The demo uses To Do, In Progress, Legal Review and Done. Each card holds the task description, assignee, priority, due date, labels and comments.

You can pin an existing board in Heym Work, share it with the team, add cards and columns, and filter the work.

There’s also a connection that developers working with MCP might find interesting: these boards can be created and managed through Heym Work’s chat, or from ChatGPT and Claude through MCP.

That gives people different ways to work with the same board. Someone can update tasks through conversation while another person uses the visual interface.

What we’re designing around

These walkthroughs cover a few practical choices:

  • Put workflow controls close to the information people need.
  • Make ownership and next actions easy to find.
  • Keep task details and discussion attached to the work.
  • Support both a visual workspace and conversational access.

The legal team, companies and records in both videos are demo data. The broader problem applies anywhere people need to run an automation, review its output and coordinate what happens next.

You can explore Heym Work or read the Heym Core source on GitHub.

If you build automations for other teams, what interface do you give them once the workflow is ready?

Top comments (0)