> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Aha!

The Aha! connector lets your AI agent act in each user's Aha! account. Each user connects their own Aha! access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 30 tools.

**Authentication:** Bearer Token
**Categories:** Project Management, Productivity
**Tools:** 30: 18 read, 11 write, 1 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=AHA)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Aha! connection

   In **AgentKit > Connections**, create an Aha! connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'aha'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Aha!:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'aha_features_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "aha"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Aha!:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="aha_features_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Aha! credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'aha_epic_get',
  toolInput: {
    epic_id: '<epic_id>',
  },
  connector: 'aha',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="aha_epic_get",
    tool_input={
        "epic_id": "<epic_id>",
    },
    connection_name="aha",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `aha_epic_get`

Get Epic · Read-only

Get one Aha! epic by ID or reference key.
Returns the epic's id, reference_num, name, description, workflow_status, release, assignee, tags, features, dates, custom fields and url.
Use List Epics to find epics.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `epic_id` (`string`, required): Numeric ID or reference key of the epic. Get it from List Epics. Example: APP-E-3.

Example input: `{"epic_id":"<epic_id>"}`

### `aha_epics_list`

List Epics · Read-only

List epics in an Aha! product, filtered by search term, tag, assignee, status or update time.
Returns pagination and epics with id, reference_num, name, created_at and url.
Use Get Epic for full details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `assigned_to_user` (`string`, optional): ID or email of a user; only epics assigned to them. Example: pm@example.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the epic name. Example: login.
- `tag` (`string`, optional): Only epics with this tag. Example: mobile.
- `updated_since` (`string`, optional): Only epics updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `workflow_status` (`string`, optional): Workflow status ID or name; only epics in that status. Example: In development.

Example input: `{"product_id":"<product_id>"}`

### `aha_feature_comments_list`

List Feature Comments · Read-only

List comments on an Aha! feature.
Returns pagination and comments with id, body, user, created_at and url.
Use Create Feature Comment to reply.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.

Example input: `{"feature_id":"<feature_id>"}`

### `aha_feature_get`

Get Feature · Read-only

Get one Aha! feature by ID or reference key.
Returns the feature's id, reference_num, name, description, workflow_status, release, epic, assignee, tags, estimates, dates, requirements, custom fields and url.
Use List Features to find features.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.

Example input: `{"feature_id":"<feature_id>"}`

### `aha_features_list`

List Features · Read-only

List features across the Aha! account, filtered by search term, tag, assignee, status, custom fields or update time.
Returns pagination and features with id, reference_num, name, created_at and url.
Use List Release Features for one release and Get Feature for full details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `assigned_to_user` (`string`, optional): ID or email of a user; only features assigned to them. Example: pm@example.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the feature name. Example: login.
- `tag` (`string`, optional): Only features with this tag. Example: mobile.
- `updated_since` (`string`, optional): Only features updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `workflow_status` (`string`, optional): Workflow status ID or name; only features in that status. Example: In development.

Example input: `{}`

### `aha_goals_list`

List Goals · Read-only

List the goals defined in an Aha! product.
Returns pagination and goals with id, reference_num, name, created_at and url.
Use this to see what features and initiatives support.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.

Example input: `{"product_id":"<product_id>"}`

### `aha_idea_comments_list`

List Idea Comments · Read-only

List internal comments on an Aha! idea.
Returns pagination and comments with id, body, user, created_at and url.
Use Get Idea for the idea itself.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `idea_id` (`string`, required): Numeric ID or reference key of the idea. Get it from List Ideas. Example: APP-I-45.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.

Example input: `{"idea_id":"<idea_id>"}`

### `aha_idea_get`

Get Idea · Read-only

Get one Aha! idea by ID or reference key.
Returns the idea's id, reference_num, name, description, workflow_status, votes, categories, tags, creator, promoted feature or epic, and url.
Use List Ideas to find ideas.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `idea_id` (`string`, required): Numeric ID or reference key of the idea. Get it from List Ideas. Example: APP-I-45.
- `fields` (`string`, optional): Comma-separated fields to return, or * for all default fields. Example: name,description,votes.

Example input: `{"idea_id":"<idea_id>"}`

### `aha_ideas_list`

List Ideas · Read-only

List ideas in an Aha! product, filtered by search term, status, tag, assignee, creator or dates, sorted by recent, trending or popular.
Returns pagination and ideas with id, name, reference_num, created_at, workflow_status, votes and url (more with fields).
Use Get Idea for full details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `assigned_to_user` (`string`, optional): ID or email of a user; only ideas assigned to them. Example: pm@example.com.
- `created_since` (`string`, optional): Only ideas created after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `fields` (`string`, optional): Comma-separated fields to return for each idea, or * for all default fields. Without it ideas come back in a minimal form. Example: name,description,votes.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the idea name. Example: login.
- `sort` (`string`, optional): Sort order: recent, trending or popular. Aha! defaults to trending. Example: recent. One of: `recent`, `trending`, `popular`.
- `spam` (`boolean`, optional): Set true to list ideas marked as spam instead. Example: true.
- `tag` (`string`, optional): Only ideas with this tag. Example: mobile.
- `updated_since` (`string`, optional): Only ideas updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `workflow_status` (`string`, optional): Workflow status ID or name; only ideas in that status. Example: In development.

Example input: `{"product_id":"<product_id>"}`

### `aha_initiatives_list`

List Initiatives · Read-only

List initiatives in an Aha! product, filtered by search term, assignee, status, active state or update time.
Returns pagination and initiatives with id, reference_num, name, created_at and url.
Use the initiative name or ID when creating features or epics.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `assigned_to_user` (`string`, optional): ID or email of a user; only initiatives assigned to them. Example: pm@example.com.
- `only_active` (`boolean`, optional): Set true to return only active initiatives. Example: true.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the initiative name. Example: login.
- `updated_since` (`string`, optional): Only initiatives updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `workflow_status` (`string`, optional): Workflow status ID or name; only initiatives in that status. Example: In development.

Example input: `{"product_id":"<product_id>"}`

### `aha_me_get`

Get Current User · Read-only

Get the Aha! user who owns the API key.
Returns the user's id, name, email, created and updated times, plus accounts or permissions when requested.
Use this to confirm the connection.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `include` (`string`, optional): Extra data to include, such as accounts or permissions. Example: accounts.

Example input: `{}`

### `aha_product_get`

Get Product · Read-only

Get one Aha! product (workspace) by ID or key.
Returns the product's id, reference_prefix, name, description, workspace type, custom fields and url.
Use List Products to find product keys.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.

Example input: `{"product_id":"<product_id>"}`

### `aha_products_list`

List Products · Read-only

List the products (workspaces) in the Aha! account.
Returns pagination and products with id, reference_prefix, name, product_line flag, created_at and url.
Use this to get the product_id the release, epic, idea, goal and initiative tools need.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `updated_since` (`string`, optional): Only products updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.

Example input: `{}`

### `aha_release_features_list`

List Release Features · Read-only

List the features in one Aha! release, with the same filters as List Features.
Returns pagination and features with id, reference_num, name, created_at and url.
Use Get Feature for full details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `release_id` (`string`, required): Numeric ID or reference key of the release. Get it from List Releases. Example: APP-R-1.
- `assigned_to_user` (`string`, optional): ID or email of a user; only features assigned to them. Example: pm@example.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the feature name. Example: login.
- `tag` (`string`, optional): Only features with this tag. Example: mobile.
- `updated_since` (`string`, optional): Only features updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.
- `workflow_status` (`string`, optional): Workflow status ID or name; only features in that status. Example: In development.

Example input: `{"release_id":"<release_id>"}`

### `aha_release_get`

Get Release · Read-only

Get one Aha! release by ID or reference key.
Returns the release's id, reference_num, name, dates, workflow_status, owner, theme, progress, feature counts and url.
Use List Releases to find releases.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `release_id` (`string`, required): Numeric ID or reference key of the release. Get it from List Releases. Example: APP-R-1.

Example input: `{"release_id":"<release_id>"}`

### `aha_releases_list`

List Releases · Read-only

List releases in an Aha! product, optionally searched or excluding shipped ones.
Returns pagination and releases with id, reference_num, name, start_date, release_date, released flag, parking_lot flag and url.
Use this to get a release_id for creating features and epics.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `exclude_shipped` (`boolean`, optional): Set true to leave out shipped releases. Example: true.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `parking_lot` (`boolean`, optional): Set true to return only parking lot releases. Example: true.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the release name. Example: login.
- `updated_since` (`string`, optional): Only releases updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.

Example input: `{"product_id":"<product_id>"}`

### `aha_requirements_list`

List Feature Requirements · Read-only

List the requirements of an Aha! feature.
Returns pagination and requirements with id, reference_num, name, created_at and url.
Use Create Requirement to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.
- `q` (`string`, optional): Search term matched against the requirement name. Example: login.
- `updated_since` (`string`, optional): Only requirements updated after this UTC ISO 8601 timestamp. Example: 2026-01-01T00:00:00Z.

Example input: `{"feature_id":"<feature_id>"}`

### `aha_users_list`

List Users · Read-only

List users in the Aha! account, optionally by email.
Returns pagination and users with id, name, email, enabled flag, created and updated times.
Use this to find someone to assign work to.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): Only the user with this email. Example: pm@example.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 2.
- `per_page` (`integer`, optional): Records per page, up to 200. Aha! defaults to 30. Example: 50.

Example input: `{}`

### `aha_epic_create`

Create Epic · Write

Create an epic in an Aha! release.
Returns the new epic with its id, reference_num and url.
Use Create Feature with the epic's name or ID to add features to it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the epic. Example: Enterprise readiness.
- `release_id` (`string`, required): Numeric ID or reference key of the release. Get it from List Releases. Example: APP-R-1.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the epic to. Example: pm@example.com.
- `description` (`string`, optional): Description of the epic; may include HTML. Example: Allow login with the customer's IdP.

- `due_date` (`string`, optional): Due date in YYYY-MM-DD format. Example: 2026-07-01.
- `initiative` (`string`, optional): Name or ID of the initiative the epic belongs to. Example: Enterprise expansion.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `workflow_status` (`string`, optional): Workflow status name to set; must be a valid status for the epic's workflow. Example: In design.

Example input: `{"name":"<name>","release_id":"<release_id>"}`

### `aha_epic_update`

Update Epic · Write

Update an Aha! epic's name, description, status, assignee, tags or dates.
Returns the updated epic.
Only the fields you pass change.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `epic_id` (`string`, required): Numeric ID or reference key of the epic. Get it from List Epics. Example: APP-E-3.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the epic to. Example: pm@example.com.
- `description` (`string`, optional): Description of the epic; may include HTML. Example: Allow login with the customer's IdP.

- `due_date` (`string`, optional): Due date in YYYY-MM-DD format. Example: 2026-07-01.
- `name` (`string`, optional): Name of the epic. Example: Enterprise readiness.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `workflow_status` (`string`, optional): Workflow status name to set; must be a valid status for the epic's workflow. Example: In design.

Example input: `{"epic_id":"<epic_id>"}`

### `aha_feature_comment_create`

Create Feature Comment · Write

Post a comment on an Aha! feature as the API key's user.
Returns the new comment with its id, body and url.
Watchers of the feature are notified by Aha!.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): Comment body; may include HTML. Example: Design review is done.

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.

Example input: `{"body":"<body>","feature_id":"<feature_id>"}`

### `aha_feature_create`

Create Feature · Write

Create a feature in an Aha! release.
Returns the new feature with its id, reference_num and url.
Features always belong to a release: use List Releases to pick one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the feature. Example: Single sign-on.
- `release_id` (`string`, required): Numeric ID or reference key of the release. Get it from List Releases. Example: APP-R-1.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the feature to. Example: pm@example.com.
- `description` (`string`, optional): Description of the feature; may include HTML. Example: Allow login with the customer's IdP.

- `detailed_estimate_text` (`string`, optional): Detailed estimate: time with min, h, d, w, m (1d = 8h, 1w = 5d) or story points with p, depending on the workspace's capacity units. Example: 2d 4h.
- `due_date` (`string`, optional): Due date in YYYY-MM-DD format. Example: 2026-07-01.
- `epic` (`string`, optional): Name or ID of the epic the feature belongs to. Example: APP-E-3.
- `initiative` (`string`, optional): Name or ID of the initiative the feature belongs to. Example: Enterprise expansion.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `workflow_status` (`string`, optional): Workflow status name to set; must be a valid status for the feature's workflow. Example: In design.

Example input: `{"name":"<name>","release_id":"<release_id>"}`

### `aha_feature_update`

Update Feature · Write

Update an Aha! feature's name, description, status, assignee, tags, dates, epic, initiative or estimate.
Returns the updated feature.
Only the fields you pass change. Tags passed here replace the existing tags.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the feature to. Example: pm@example.com.
- `description` (`string`, optional): Description of the feature; may include HTML. Example: Allow login with the customer's IdP.

- `detailed_estimate_text` (`string`, optional): Detailed estimate: time with min, h, d, w, m (1d = 8h, 1w = 5d) or story points with p, depending on the workspace's capacity units. Example: 2d 4h.
- `due_date` (`string`, optional): Due date in YYYY-MM-DD format. Example: 2026-07-01.
- `epic` (`string`, optional): Name or ID of the epic the feature belongs to. Example: APP-E-3.
- `initiative` (`string`, optional): Name or ID of the initiative the feature belongs to. Example: Enterprise expansion.
- `name` (`string`, optional): Name of the feature. Example: Single sign-on.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `workflow_status` (`string`, optional): Workflow status name to set; must be a valid status for the feature's workflow. Example: In design.

Example input: `{"feature_id":"<feature_id>"}`

### `aha_idea_create`

Create Idea · Write

Create an idea in an Aha! product on behalf of a person, who need not be an Aha! user.
Returns the new idea with its id, reference_num and url.
Set visibility to control who can see it; Aha! defaults to internal only.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `created_by` (`string`, required): Email of the person who submitted the idea; does not need to be an Aha! user. Example: customer@example.com.
- `name` (`string`, required): Name of the idea. Example: Dark mode.
- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the idea to. Example: pm@example.com.
- `categories` (`string`, optional): Existing idea category names, comma-separated. Example: Integrations,Reporting.
- `description` (`string`, optional): Description of the idea; may include HTML. Example: Allow login with the customer's IdP.

- `initial_votes` (`integer`, optional): Number of votes to seed the idea with, when importing. Example: 3.
- `submitted_idea_portal_id` (`string`, optional): Numeric ID of the ideas portal the idea was submitted through. Recommended when the creator is a portal user. Example: 6776223543364558541.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `visibility` (`string`, optional): Who can see the idea: aha (internal only, the default), creator, employee, employee_or_creator, creator_organization or public. Example: public. One of: `aha`, `creator`, `employee`, `employee_or_creator`, `creator_organization`, `public`.
- `workflow_status` (`string`, optional): Idea status name; must exist in the product's idea workflow. Example: Under consideration.

Example input: `{"created_by":"<created_by>","name":"<name>","product_id":"<product_id>"}`

### `aha_idea_promote`

Promote Idea · Write

Promote an Aha! idea into a feature, epic, initiative or requirement linked to the idea.
Returns the idea with its promoted record.
Features and epics need release_id, requirements need feature_id, initiatives need product_id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `idea_id` (`string`, required): Numeric ID or reference key of the idea. Get it from List Ideas. Example: APP-I-45.
- `promotable_type` (`string`, required): What to promote the idea to: feature, epic, initiative or requirement. Example: feature. One of: `feature`, `epic`, `initiative`, `requirement`.
- `feature_id` (`string`, optional): Feature ID or key; required when promoting to a requirement. Example: APP-12.
- `product_id` (`string`, optional): Product ID or key; required when promoting to an initiative. Example: APP.
- `release_id` (`string`, optional): Release ID or key; required when promoting to a feature or epic. Example: APP-R-1.

Example input: `{"idea_id":"<idea_id>","promotable_type":"feature"}`

### `aha_idea_update`

Update Idea · Write

Update an Aha! idea's name, description, status, tags, categories, assignee or visibility.
Returns the updated idea.
Only the fields you pass change. Use Promote Idea to turn it into a feature or epic.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `idea_id` (`string`, required): Numeric ID or reference key of the idea. Get it from List Ideas. Example: APP-I-45.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the idea to. Example: pm@example.com.
- `categories` (`string`, optional): Existing idea category names, comma-separated. Example: Integrations.
- `description` (`string`, optional): Description of the idea; may include HTML. Example: Allow login with the customer's IdP.

- `name` (`string`, optional): Name of the idea. Example: Dark mode.
- `tags` (`string`, optional): Tags as comma-separated values. Example: mobile,security.
- `visibility` (`string`, optional): Who can see the idea: aha, creator, employee, employee_or_creator, creator_organization or public. Example: public. One of: `aha`, `creator`, `employee`, `employee_or_creator`, `creator_organization`, `public`.
- `workflow_status` (`string`, optional): Idea status name. Example: Planned.

Example input: `{"idea_id":"<idea_id>"}`

### `aha_release_create`

Create Release · Write

Create a release in an Aha! product.
Returns the new release with its id, reference_num, name, dates and url.
Use Create Feature or Create Epic to add work to it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the release. Example: Q3 2026.
- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `owner` (`string`, optional): Email or ID of the release owner. Example: pm@example.com.
- `parking_lot` (`boolean`, optional): Set true to make it a parking lot release for unscheduled work. Example: false.
- `release_date` (`string`, optional): Release date in YYYY-MM-DD format. Example: 2026-07-01.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `theme` (`string`, optional): Theme of the release; may include HTML. Example: Enterprise readiness

- `workflow_status` (`string`, optional): Workflow status name for the release. Example: Planning.

Example input: `{"name":"<name>","product_id":"<product_id>"}`

### `aha_release_update`

Update Release · Write

Update an Aha! release's name, owner, theme, status or dates.
Returns the updated release.
Only the fields you pass change.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): Numeric ID or key of the Aha! product (workspace). Get it from List Products. Example: APP.
- `release_id` (`string`, required): Numeric ID or reference key of the release. Get it from List Releases. Example: APP-R-1.
- `name` (`string`, optional): Name of the release. Example: Q3 2026.
- `owner` (`string`, optional): Email or ID of the release owner. Example: pm@example.com.
- `release_date` (`string`, optional): Release date in YYYY-MM-DD format. Example: 2026-07-01.
- `start_date` (`string`, optional): Start date in YYYY-MM-DD format. Example: 2026-07-01.
- `theme` (`string`, optional): Theme of the release; may include HTML. Example: Enterprise readiness

- `workflow_status` (`string`, optional): Workflow status name for the release. Example: Shipped.

Example input: `{"product_id":"<product_id>","release_id":"<release_id>"}`

### `aha_requirement_create`

Create Requirement · Write

Add a requirement (sub-item) to an Aha! feature.
Returns the new requirement with its id, reference_num and url.
Use List Feature Requirements to see existing ones.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.
- `name` (`string`, required): Name of the requirement. Example: SAML support.
- `assigned_to_user` (`string`, optional): Email address of the Aha! user to assign the requirement to. Example: pm@example.com.
- `description` (`string`, optional): Description of the requirement; may include HTML. Example: Allow login with the customer's IdP.

- `workflow_status` (`string`, optional): Workflow status name to set; must be a valid status for the requirement's workflow. Example: In design.

Example input: `{"feature_id":"<feature_id>","name":"<name>"}`

### `aha_feature_delete`

Delete Feature · Destructive

Delete an Aha! feature with its requirements.
Returns an empty response on success.
Deleted records go to the Aha! recycle bin.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `feature_id` (`string`, required): Numeric ID or reference key of the feature. Get it from List Features. Example: APP-12.

Example input: `{"feature_id":"<feature_id>"}`

## Related

Other Project Management connectors ([all 67](/agentkit/connectors/?category=project-management)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools
- [Airtable](/agentkit/connectors/airtable/): Scalekit connector, OAuth, 26 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
