Kitemaker n8n integrationAutomate Kitemaker with n8n.
A work item can be created, read back and updated by a workflow instead of a person. The Kitemaker n8n integration carries 7 operations over 4 resources, on top of the Kitemaker GraphQL API: organization, space, user and work item. No trigger ships with it, so another node starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Kitemaker n8n integration actually do?
The Kitemaker n8n integration links your Kitemaker organization to n8n, the automation tool you can self-host with Docker or npm, or run on n8n Cloud. The node talks to the Kitemaker GraphQL API and exposes 7 operations across 4 resources, so a workflow can create a work item, read one back, update it, and list the spaces and users of the logged-in organization.
Start with intake. A form submission, an inbound email or a message from a teammate has to become a work item before anyone forgets about it. workItem.create asks for a title, a space and a status, and the item lands where triage happens. Most teams put Slack at the other end of that workflow so the person who reported the issue sees an answer in the same thread.
Then reporting. workItem.getAll pulls the items of one space, user.getAll pulls the people in the organization, and both land in a spreadsheet nobody has to fill by hand. Google Sheets works for a quick weekly read, and Notion works when the summary has to sit next to the rest of the team documentation.
Third, keeping two tools honest. An item that moves in another tracker rarely moves in Kitemaker at the same time. A workflow that reads the change and calls workItem.update closes that gap, and because the update fields are optional, it can touch the status without rewriting the title or the description.
When an operation you need is not among the 7, the HTTP Request node calls any endpoint of the Kitemaker API and reuses the same credential through predefined authentication. That is the standard way out of a dedicated node, and it keeps the token in one place.
Two things to plan for. Reading lists is paginated: with Return All switched off, Limit decides how many items the node returns, which is fine for a preview and wrong for an export. And a field marked as required blocks the node when it is empty, so a missing title stops the run rather than creating something half built. If that part of n8n is new to you, the n8n training covers expressions and credentials before you wire anything to a live workspace.
How do you connect Kitemaker to n8n?
- 01
Create the Kitemaker account
The credential documentation lists one prerequisite: a Kitemaker account. The node authenticates as the account that generated the token, which is why several operations are described as acting on the logged-in user's organization. Decide upfront whether the automation should run under a personal account or a dedicated one, because every item it creates will carry that identity.
- 02
Generate the personal access token
Kitemaker supports one authentication method for n8n: an API access token. Open Manage > Developer settings in Kitemaker and generate a Personal Access Token. Kitemaker's API authentication documentation walks through the same path in more detail. Copy the value straight away and keep it somewhere you control, since a token is the only thing standing between a workflow and your work items.
- 03
Save the credential in n8n
In n8n, open the Credentials menu and create a Kitemaker credential, which is the stored login n8n reuses on your behalf. Paste the personal access token, save, then open any Kitemaker node: the credential appears in its dropdown. You create it once and every workflow in the instance can select it, on n8n Cloud and on a self-hosted instance alike.
What can the Kitemaker node do in n8n?
The Kitemaker node exposes 7 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Organization
1 operationGet the logged-in user's organization
organization.getWhat you see in n8n
Notes & use cases
This operation retrieves data on the organization behind the token you connected, and returns it as one item. Nothing to configure, which makes it the cheapest way to prove a credential still works.
Space
1 operationGet many spaces
space.getAllWhat you see in n8n
Notes & use cases
Spaces are how Kitemaker separates streams of work. This operation retrieves data on many spaces in the logged-in user's organization, each one arriving as its own item, ready to loop over.
Key parameters
- Return All: switched on, n8n walks the API pages and brings back every space; switched off, Limit sets how many spaces leave the node.
User
1 operationGet many users
user.getAllWhat you see in n8n
Notes & use cases
Instead of keeping a hand written list of teammates somewhere, ask Kitemaker. The operation retrieves data on many users in the logged-in user's organization, one item per person.
Key parameters
- Return All: on, the node pages through the whole roster; off, Limit caps the number of users returned, which is enough for a spot check.
Work Item
4 operationsCreate a work item
workItem.createWhat you see in n8n
Notes & use cases
Here is where most Kitemaker workflows end: the node creates the item, and the run has produced something visible to the team.
Key parameters
- Title: title of the work item to create, usually an expression such as
{{ $json.field }}pulling from the previous node. - Space Name or ID: pick the space from the list, or pass an ID with an expression when it changes per run.
- Status Name or ID: the status set on the new item, same choice between list and expression.
- Additional Fields: 5 optional fields, including Description, which supports Markdown.
Get a work item
workItem.getWhat you see in n8n
Notes & use cases
One item, by its identifier. Useful when a later step needs the current state of a single work item rather than a list it has to filter.
Key parameters
- Work Item ID: the ID of the work item to retrieve. It is required, so an empty value stops the node; feed it with an expression like
{{ $json.field }}when it comes from an earlier node.
Get many work items
workItem.getAllWhat you see in n8n
Notes & use cases
Reading a whole stream of work at once, rather than one item at a time, is what this operation is for. It returns the work items of a given space.
Key parameters
- Space Name or ID: required, the ID of the space to retrieve the work items from. Choose it from the list or specify the ID with an expression.
- Return All: on for a complete export; off, and Limit decides how many items come back.
Update a work item
workItem.updateWhat you see in n8n
Notes & use cases
Changing an existing item beats creating a duplicate one. The node updates the work item you point it at, and leaves alone every field you do not fill.
Key parameters
- Work Item ID: required, the ID of the work item to update.
- Update Fields: 5 optional fields, among them Status Name or ID, Title and Description, which supports Markdown.
Need help automating Kitemaker with n8n?
A person reads every message.
Kitemaker and n8n, the questions that come next
01Is the Kitemaker n8n integration free?
02What credentials do you need to connect Kitemaker to n8n?
03What are the limits of the Kitemaker node in n8n?
04Does the Kitemaker node react in real time?
05n8n or Make for Kitemaker?
Get our weekly integration tips.
No spam. Unsubscribe anytime.
