Kaiten icon

Kaiten

Interact with Kaiten API (read operations only)
Join our community

Actions8

Overview

This node integrates with the Kaiten API to retrieve information about boards within a specified space. The "Get All" operation for the "Board" resource fetches all boards that belong to a selected space. This is useful when you want to list or process multiple boards from a particular workspace or project area in Kaiten.

Practical examples include:

  • Automating reporting by retrieving all boards in a space and summarizing their statuses.
  • Syncing board data with other tools or databases.
  • Triggering workflows based on the collection of boards available in a given space.

Properties

Name Meaning
Space Select a space to get boards from. This property lets you specify which Kaiten space's boards you want to retrieve. The options are dynamically loaded from your Kaiten account spaces.

Output

The output is an array of JSON objects, each representing a board retrieved from the specified space. Each object contains the full details of a board as returned by the Kaiten API, including properties such as board ID, title, and other metadata.

The output structure looks like this (example):

[
  {
    "id": "123",
    "title": "Project Board A",
    "description": "...",
    "created_at": "...",
    ...
  },
  {
    "id": "456",
    "title": "Project Board B",
    "description": "...",
    "created_at": "...",
    ...
  }
]

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Kaiten API.
  • The node makes HTTP GET requests to the Kaiten API endpoints.
  • The user must have access rights to the specified space in Kaiten.
  • The node depends on n8n's built-in HTTP request helper with authentication support.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Selecting a space without any boards will return an empty result.
    • Network connectivity issues can prevent successful API calls.
    • If the space ID is invalid or the user lacks permission, the API may return errors.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • "Not Found" or similar errors suggest the space ID does not exist or is inaccessible.
    • Unexpected response format errors may occur if the API changes; ensure the node and credentials are up to date.

  • Resolution tips:

    • Confirm API credentials are correct and have necessary permissions.
    • Verify the selected space exists and contains boards.
    • Check network connectivity and proxy settings if applicable.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion