Actionist·Kitemaker

Kitemaker

· #306 most-used

End-to-end product development from user feedback to shipped features

CommunicationProductivityProjectsDeveloperAutomation

Kitemaker was a collaborative product development tool built for software teams who wanted to plan, prioritise, and execute work in a single shared space — not siloed across separate tools for each role. It combined work-item tracking, roadmapping, and user-feedback capture with a GraphQL API that let teams automate creation, updates, and retrieval of work items, spaces, and users. Kitemaker was acquired by ClickUp and the service was discontinued on September 1st 2025; teams that integrated with Kitemaker via API may now be migrating those workflows to ClickUp.

Try Kitemaker with ActionistVisit Kitemaker
Average time saved
7 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of transcribing bugs from support tools, chasing status updates from engineering, compiling progress digests by hand, and routing unassigned work items across spaces.

Schedule

What your Kitemaker agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Kitemaker × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~13 hrsSaved / week
6Personas served
For engineering
Featured4 apps

GitHub PR merged triggers work item status update and release note draft

When a GitHub pull request is merged, the operations agent updates the linked Kitemaker work item to Done, adds a comment with the PR details for full traceability, drafts a changelog entry in Notion, and posts a ship notification to Slack — all within about a minute of the merge, with zero manual steps from the engineering team.

~3 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a pull request referencing a Kitemaker work item ID is merged on GitHub
Trigger
Step 1
GitHub
Detect merged pull request with Kitemaker item ID in branch name or PR body
read
Step 2
Kitemaker
Get Work Item to confirm current status and retrieve full description
write
Step 3
Kitemaker
Update Work Item Status to Done
write
Step 4
Kitemaker
Create Comment with the merged PR URL, commit SHA, and merge timestamp
write
Step 5
Notion
Append one-sentence changelog entry to the current sprint's release note draft
write
Step 6
Slack
Post ship notification to #engineering with the work item title and PR link
Result
Update Work Item Status to DoneCreate Comment with the merged PR URL, commit SHA, and merge timestampAppend one-sentence changelog entry to the current sprint's release note draftPost ship notification to #engineering with the work item title and PR link
The win
Saved per run
8 min
Runs / week
~25×
Every shipped item is closed and documented automatically at merge time
Driven byOperations Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    30 min / week
    Manual feature request transcription and follow-up

    Reps write feature requests in CRM notes, email the product team, and manually chase for status updates — creating duplicated work and no structured record in the tracker.

    Sales Agent
    0 min
    Agent logs and monitors deal-critical features automatically

    When a rep flags a feature as deal-critical in the CRM, the agent creates a Kitemaker work item, links it back to the deal, and alerts the product team in Slack within about a minute.

  • Marketing
    60 min / week
    Manual changelog gathering from engineering

    The marketing writer emails each engineering lead asking what shipped this week, waits for replies, formats the responses into changelog prose, and then chases for missing context — every release cycle.

    Marketing Agent
    0 min
    Agent compiles launch-ready changelog from live tracker data

    The marketing agent sweeps completed work items weekly, drafts one-sentence changelog entries from item titles and descriptions, and stages them in Notion before the writer even opens their laptop.

  • Customer Support
    45 min / week
    Manual bug transcription from ticket to tracker

    Support agents copy bug details from tickets into Kitemaker manually, losing formatting, forgetting reproduction steps, and creating duplicate items when multiple agents hit the same bug.

    Customer Support Agent
    0 min
    Agent creates and links bug work items from support tickets

    When a ticket is tagged as a confirmed bug, the agent creates a Kitemaker work item with full reproduction context and writes the item ID back to the ticket so support and engineering are always linked.

  • Human Resources
    25 min / week
    Manual onboarding checklist setup per new hire

    HR creates a new checklist manually in Kitemaker (or forgets to) for each new hire, copying from a template, setting assignees, and then following up individually to check task completion.

    Human Resources Agent
    0 min
    Agent creates onboarding and offboarding checklists on day one

    When a new engineer is confirmed in the HRIS, the agent creates the full onboarding task set in Kitemaker, assigns each item, and notifies the new hire and manager — before the engineer's first standup.

  • Finance
    40 min / week
    Manual engineering cost estimation from team reports

    Finance asks engineering leads to estimate hours and costs per initiative in a spreadsheet each week — responses are delayed, estimates are inconsistent, and the data is always at least a week stale.

    Finance Agent
    0 min
    Agent produces initiative cost attribution from live tracker data

    Every Monday, the finance agent counts completed work items per initiative, estimates engineering cost per item, and updates the cost-attribution spreadsheet before the leadership meeting — no engineer input required.

  • Operations
    60 min / week
    Manual backlog grooming and assignment reviews

    An engineering manager or EM manually reviews all active spaces for stale items, DMs assignees individually, checks who is free, and reassigns items — a task that takes an hour and still gets deprioritised.

    Operations Agent
    0 min
    Agent sweeps stale items and routes unassigned work weekly

    Every Monday, the operations agent identifies all stale in-progress items, applies a stale label, posts a comment requesting an update, and routes all unassigned items to the engineer with the lightest load.

  • Legal
    35 min / week
    Manual legal-to-engineering compliance handoff

    Legal emails engineering with a list of regulatory requirements, waits for confirmation that items are logged in the tracker, and then follows up manually to check progress as deadlines approach.

    Legal Agent
    0 min
    Agent logs compliance obligations into the engineering tracker immediately

    When legal identifies a new regulatory requirement, the agent creates a Kitemaker work item with the deadline, jurisdiction, and required action, assigns it to the compliance engineering lead, and sets a 21-day calendar reminder.

+ 100s of other Kitemaker automations
Average time saved
30 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
9
Hours saved / year
450
Annual ROI
$33,750

Based on Kitemaker's typical team usage — the visible tasks plus a few other automations the agent runs: ~1.8 hrs / person / week of admin work automated.

Connect

How to plug Kitemaker into Actionist

Pick the connection method that suits your environment.

Authenticate with a Kitemaker personal access token. The token operates as the generating user and has access to every space that user can see.

1
Open Kitemaker Settings

Log in to your Kitemaker workspace, click your avatar in the top-left corner, and go to Settings → API.

2
Generate a personal access token

Click Generate token. Give it a descriptive name (e.g. "Actionist") and copy the token — it will only be shown once.

3
Paste into Actionist

Enter the token in the field below and click Test connection. Actionist will call the organization endpoint to verify access.

Credentials you'll need
API access token*
Kitemaker → Settings → API → Generate personal access token
Actions

14 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

0 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

This app has no triggers yet.
FAQs

Questions about Kitemaker + Actionist

How does Actionist connect to Kitemaker?
Go to the Apps tab, find Kitemaker, and click Connect. You will need a personal access token generated in Kitemaker under Settings → API. Paste the token into the API access token field and click Test connection — Actionist calls the organization endpoint to confirm access before any actions run. Note that Kitemaker was acquired by ClickUp and discontinued on September 1st 2025; if you are migrating workflows built against the Kitemaker GraphQL API, those same patterns translate directly to the ClickUp integration in Actionist.
What API operations does Actionist support for Kitemaker?
Actionist supports the core read and write operations exposed by the Kitemaker GraphQL API: retrieving your organization, listing all spaces and users, creating work items, fetching individual or all work items in a space, updating work item fields (title, description, status, labels, assignees), adding comments, and reading initiatives, feedback items, and space-level statuses and labels. There are no webhook-based triggers available in the Kitemaker API, so all scheduled data pulls run as agent tasks on a cadence you define.
Can I use Actionist to automatically create Kitemaker work items from other tools?
Yes — this is one of the most common patterns. Connect Actionist to your help desk (e.g. Zendesk), CI/CD pipeline (GitHub Actions), or form tool (Typeform), and configure the agent to call Create Work Item in Kitemaker whenever a trigger condition is met — a confirmed bug, a failed build, a user feedback submission. The agent calls Get All Spaces first to route the item to the correct space, then creates the work item with the full context from the source tool. The Kitemaker item ID is written back to the source so both systems stay linked.
Does Actionist support updating work item status when a pull request is merged?
Yes. Connect Actionist to your GitHub or GitLab account alongside Kitemaker. When a pull request referencing a Kitemaker work item ID (usually embedded in the branch name or PR body) is merged, the agent calls Get Work Item to confirm the current status, then Update Work Item Status to move it to Done, and Create Comment to attach the PR URL and merge timestamp. The tracker reflects the real state of the code within about a minute of the merge — no developer needs to update Kitemaker manually.
Can Actionist pull weekly progress reports from Kitemaker without anyone writing them?
Yes. Schedule a weekly agent task that calls Get All Work Items across your active spaces, filters for items that changed status in the past 7 days, and groups them by initiative via Get Initiatives. The agent formats the result as a plain-English progress digest — items completed, items in review, items newly created — and posts it to Slack or appends it to a shared Notion doc. The digest is built from what is actually in the tracker, not from what someone remembered to type.
How do I route work items to the right space without hardcoding space IDs?
Use the Get All Spaces action before every Create Work Item call. The agent retrieves the current list of spaces and matches the incoming item's product area, team tag, or category to the closest space name. This makes your workflows resilient to space renames or restructures — the agent always works from live space names rather than IDs stored in the workflow definition that can go stale.
What happens to my Kitemaker integration now that the service has been discontinued?
Kitemaker was discontinued on September 1st 2025 following its acquisition by ClickUp. If you built automation workflows against the Kitemaker GraphQL API, those workflows will no longer execute against live data. Actionist has a ClickUp integration that covers the same work-item management patterns — creating tasks, updating statuses, reading workspace members, and adding comments. The migration is a reconfiguration of your existing workflows to point to ClickUp rather than a rebuild from scratch.
Does Actionist support loading work items based on space labels or statuses dynamically?
Yes. Use Get Space Labels to retrieve the current label list for a space before applying any label in a Create Work Item or Update Work Item call. Similarly, use Get Space Statuses to resolve human-readable status names (like 'QA Ready' or 'In Review') to their Kitemaker status IDs before an Update Work Item Status call. This keeps your agent workflows portable across different Kitemaker workspaces that may have different label and status configurations.