> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/project-management/aha.md).

# Aha

Connect Aha product management data to Google Sheets, BigQuery, or data warehouses via Coupler.io. Pull features, goals, ideas, and roadmap data automatically.

Aha is a product management platform that helps teams build and roadmap products, track features, collect ideas, and align strategy with execution. It's widely used by product managers to manage everything from high-level goals down to individual feature details.

Connecting Aha to Coupler.io lets you pull your product data into spreadsheets, BI tools, or data warehouses — automatically and on a schedule.

## Why connect Aha to Coupler.io?

* **Centralize your product data** — combine Aha data with data from other tools like Jira, Slack, or Google Sheets
* **Automate reporting** — schedule regular data refreshes so your dashboards stay up to date without manual exports
* **Analyze ideas and feedback** — track endorsements, comments, and idea categories to understand what your users want
* **Monitor goals and features** — report on strategic objectives alongside feature progress in one place

## Prerequisites

Before connecting, make sure you have:

* An active Aha account with access to the workspace you want to pull data from
* An Aha API key (available in your Aha profile settings)
* Your Aha domain (the subdomain part of your Aha URL, e.g., `yourcompany.aha.io`)

## Quick start

{% hint style="success" %}
Start with the **Features streams** or **Ideas streams** entity — these are most useful for product reporting and a good way to verify your connection is working correctly.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Go to Coupler.io and create a new data flow.** Search for **Aha** as your source.
{% endstep %}

{% step %}
**Enter your Aha API key.** In Aha, go to your profile settings and navigate to **Developer > API key**. Copy the key and paste it into the Coupler.io connection screen.
{% endstep %}

{% step %}
**Enter your Aha domain.** This is the subdomain from your Aha URL — for example, if your workspace URL is `yourcompany.aha.io`, enter `yourcompany`.
{% endstep %}

{% step %}
**Select an entity.** Choose which type of data you want to import (see the table below for options). You can create separate importers for different entities.
{% endstep %}

{% step %}
**Configure your destination.** Choose where to send the data (e.g., Google Sheets, BigQuery, Excel, ChatGPT).
{% endstep %}
{% endstepper %}

## Aha data overview

When you connect Aha to Coupler.io, you can pull data from eight different entities. Each entity maps to a specific area of your Aha workspace — from product features and strategic goals to user ideas and community feedback.

## Available entities

| Entity                    | What it contains                                                         |
| ------------------------- | ------------------------------------------------------------------------ |
| Features streams          | Individual features, their status, release assignments, and details      |
| Products streams          | Product records including names, descriptions, and configuration         |
| Idea categories streams   | The category labels used to organize ideas in your workspace             |
| Ideas streams             | Submitted ideas including title, description, status, and submitter info |
| Idea endorsements streams | Votes and endorsements on ideas, including who endorsed them             |
| Idea comments streams     | Comments left on ideas by users and team members                         |
| Users streams             | Workspace users and their profile information                            |
| Goals streams             | Strategic goals and objectives with status and ownership details         |

## Features streams

#### Key fields

| Field              | Description                             |
| ------------------ | --------------------------------------- |
| `id`               | Unique identifier for the feature       |
| `name`             | Feature name or title                   |
| `reference_num`    | Aha reference number (e.g., PROD-123)   |
| `status`           | Current workflow status                 |
| `created_at`       | Date the feature was created            |
| `updated_at`       | Date the feature was last updated       |
| `product_id`       | The product this feature belongs to     |
| `release`          | Release the feature is assigned to      |
| `assigned_to_user` | Team member responsible for the feature |

## Products streams

#### Key fields

| Field              | Description                                       |
| ------------------ | ------------------------------------------------- |
| `id`               | Unique product identifier                         |
| `name`             | Product name                                      |
| `reference_prefix` | The prefix used in reference numbers (e.g., PROD) |
| `created_at`       | Date the product was created                      |

## Ideas streams

#### Key fields

| Field                   | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| `id`                    | Unique idea identifier                                 |
| `name`                  | Idea title                                             |
| `description`           | Full idea description                                  |
| `status`                | Current idea status (e.g., new, under review, shipped) |
| `created_at`            | Date the idea was submitted                            |
| `updated_at`            | Date the idea was last updated                         |
| `votes`                 | Total vote count                                       |
| `submitted_idea_portal` | Portal through which the idea was submitted            |
| `categories`            | Categories assigned to the idea                        |

## Idea endorsements streams

#### Key fields

| Field        | Description                    |
| ------------ | ------------------------------ |
| `id`         | Unique endorsement identifier  |
| `idea_id`    | The idea that was endorsed     |
| `user_id`    | The user who endorsed the idea |
| `created_at` | Date of the endorsement        |

## Goals streams

#### Key fields

| Field         | Description                 |
| ------------- | --------------------------- |
| `id`          | Unique goal identifier      |
| `name`        | Goal name                   |
| `description` | Goal description            |
| `status`      | Current status of the goal  |
| `created_at`  | Date the goal was created   |
| `product_id`  | Product the goal belongs to |

## Common field combinations

Here are some useful ways to combine fields across entities:

* **Feature progress by product** — join `features_stream` with `products_stream` on `product_id` to see how features are distributed across products
* **Idea traction** — combine `ideas_stream` with `idea_endorsements_stream` on `idea_id` to rank ideas by engagement
* **Idea feedback summary** — join `ideas_stream` with `idea_comments_stream` to see which ideas are generating the most discussion
* **Goal alignment** — link `goals_stream` and `features_stream` via `product_id` to map features back to strategic objectives

## Use cases by role

{% tabs %}
{% tab title="Product managers" %}

* Track feature status and release assignments across all products in one report
* Monitor how many features are in each workflow stage to spot bottlenecks
* Link features back to strategic goals to demonstrate roadmap alignment
* Export features data to share progress updates with stakeholders outside Aha
  {% endtab %}

{% tab title="Customer success" %}

* Pull ideas and endorsements to understand which customer requests have the most momentum
* Monitor idea comments to stay on top of customer conversations and feedback themes
* Track idea status changes over time to report back to customers when their suggestions are acted on
  {% endtab %}

{% tab title="Leadership" %}

* Report on strategic goals and their current status across all products
* Combine goals and features data to see how well execution aligns with strategy
* Use products and users' data for workspace audits and capacity planning
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Aha uses a subdomain-based URL structure — make sure you enter only the subdomain (not the full URL) when connecting
* API access may be restricted depending on your Aha plan — check that your account has API access enabled before connecting
* Fields like `description` may contain HTML formatting from the Aha editor, which will appear as raw HTML in your export
* Deleted or archived records may not appear in streams depending on your Aha workspace settings
* The `reference_num` field (e.g., PROD-123) is useful as a human-readable, unique key when building reports

## Aha common issues

### Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you copied the full API key from Aha without any trailing spaces. You can find your API key in Aha under **Profile settings > Developer > API key**. If the key has been regenerated recently, make sure you're using the latest version. Also, confirm that your Aha account has API access enabled — some lower-tier plans may restrict this.

</details>

<details>

<summary>I'm getting a "domain not found" or "invalid domain" error</summary>

Make sure you're entering only the subdomain portion of your Aha URL. For example, if your workspace is at `yourcompany.aha.io`, enter `yourcompany` — not the full URL. Including `https://` or `.aha.io` in the domain field will cause the connection to fail.

</details>

### Missing data

<details>

<summary>Some features or ideas aren't showing up in my export</summary>

Aha may not return archived or deleted records through the API. Check whether the missing items have been archived in your Aha workspace. Also, verify that the records belong to the product or workspace your API key has access to — if your key is scoped to a specific workspace, records outside that scope won't appear.

</details>

<details>

<summary>Idea endorsements or comments are empty even though I can see them in Aha</summary>

Endorsements and comments are separate entities in Coupler.io — they won't appear in the Ideas stream. Make sure you've set up separate sources for **Idea endorsements streams** and **Idea comments streams** if you need that data.

</details>

### Permission errors

<details>

<summary>I'm getting a 403 or "unauthorized" error</summary>

This usually means the API key doesn't have sufficient permissions to access the requested data. Make sure the Aha user account associated with the API key has the appropriate role in the workspace. Admin or product owner roles typically have the broadest API access. If you're on a team plan, check with your Aha administrator to confirm API access is enabled for your account.

</details>

### Data discrepancies

<details>

<summary>The feature count in Coupler.io doesn't match what I see in Aha</summary>

This can happen if your Aha view is filtered (e.g., by release, assignee, or status) while the API returns all records. Check whether any filters are applied in your Aha workspace view that wouldn't apply to the API. Also, confirm you're looking at the same product — if you have multiple products, the API will return features across all of them.

</details>

<details>

<summary>Description fields contain HTML tags instead of plain text</summary>

Aha stores rich text descriptions with HTML formatting. This is expected behavior — the API returns the raw HTML. If you need plain text, you'll need to strip the HTML tags after export using a formula or data transformations in your destination tool.

</details>

### Rate limits

<details>

<summary>My import is failing or timing out for large workspaces</summary>

Aha enforces API rate limits that can slow down or interrupt large data pulls. If you have a large workspace with thousands of features or ideas, try scheduling your data flows during off-peak hours. If the issue persists, consider splitting your imports across multiple data flows by entity type to reduce the load per sync.

</details>

## Aha FAQ

<details>

<summary>Where do I find my Aha API key?</summary>

Log in to Aha and click on your profile avatar in the top right corner. Go to **Profile settings**, then navigate to the **Developer** section. You'll find your API key there. If you don't see a Developer section, your plan may not include API access — check with your Aha administrator.

</details>

<details>

<summary>What do I enter as the Aha domain?</summary>

Enter only the subdomain part of your Aha workspace URL. If your workspace URL is `yourcompany.aha.io`, you would enter `yourcompany`. Do not include `https://` or `.aha.io`.

</details>

<details>

<summary>Can I pull data from multiple Aha products at once?</summary>

Yes. The Aha API returns data across all products your API key has access to. When you import **Features streams** or **Ideas streams**, you'll get records from all accessible products in one go. You can then filter by `product_id` on the Data sets step or in your destination tool to focus on a specific product.

</details>

<details>

<summary>Why do I see HTML tags in my description fields?</summary>

Aha stores rich text content as HTML. This is how the Aha API returns it, and Coupler.io passes it through as-is. To get plain text, use a formula or text-cleaning function in your destination tool (e.g., a `REGEXREPLACE` in Google Sheets or a transformation in your BI tool) to strip the HTML tags.

</details>

<details>

<summary>Can I get idea votes or endorsement counts?</summary>

Yes. The **Ideas streams** entity includes a `votes` field with the total count. If you need to see who endorsed each idea (user-level detail), set up a separate source for **Idea endorsements streams** and join it to your ideas data on `idea_id` on the Data sets step.

</details>

<details>

<summary>How do I connect features to strategic goals?</summary>

Both **Features streams** and **Goals streams** include a `product_id` field. You can join them on `product_id` to understand which features belong to products that have associated goals. For tighter goal-to-feature mapping, check if your Aha workspace uses the goals relationship field on feature records.

</details>

<details>

<summary>Will archived or deleted records appear in my data flows?</summary>

Generally, no. The Aha API typically only returns active records. If you're missing records you expect to see, check whether they've been archived in your Aha workspace. There's currently no option in Coupler.io to specifically request archived records from Aha.

</details>

<details>

<summary>How often can I refresh my Aha data?</summary>

Coupler.io supports flexible scheduling — from every 15 minutes to weekly. However, Aha enforces API rate limits, so very frequent refreshes on large workspaces may cause issues. A daily or hourly schedule works well for most teams.

{% hint style="info" %}
For tips on scheduling and rate limit management, see the [Best Practices](https://docs.coupler.io/sources/category/project-management/aha/best-practices.md) article. For connection or missing data problems, check [Common Issues](#aha-common-issues).
{% endhint %}

</details>

<details>

<summary>What's the difference between Ideas streams and Idea categories streams?</summary>

**Ideas streams** contain the actual ideas — titles, descriptions, statuses, votes, and so on. **Idea categories streams** contain only the category labels used to tag and organize those ideas. You'd typically use categories as a reference table to enrich your ideas data with human-readable category names.

{% hint style="info" %}
For a full breakdown of all available fields per entity, see the [Data Overview](#aha-data-overview) article.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/project-management/aha.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
