Aha!

Aha! is a cloud-based product development platform that provides tools for capturing ideas, prioritizing features, and managing product roadmaps. The Glean Aha! connector indexes content from Aha! Ideas and Aha! Features, enabling users to search and retrieve this information directly within Glean. This documentation details supported capabilities, configuration requirements, and setup procedures for the connector.

Supported features

The connector supports ingesting data from key Aha! modules, specifically Ideas and Features. The integration ensures that metadata such as titles, descriptions, comments, status, and votes are indexed and searchable. Permissions from Aha! are taken into account so users only see content they are entitled to access.

Supported objects

Object	Description
Ideas	Crowd-sourced feedback, tickets, and suggestions with metadata such as votes, comments, status, and categories.
Features	Items representing product tasks or enhancements, with fields for timelines, status, comments, goals, and tags.

Supported API endpoints

• Ideas endpoint: Fetches ideas including title, description, votes (count), author, assignee, comments, status, and related metadata.
• Features endpoint: Retrieves features with similar metadata fields to ideas, plus associated release and goal information.
• User and permission endpoints: Identifies workspace (product) memberships and role-based access for permission enforcement.
• Incremental data fetching using updated timestamps (updated_since parameter).
• Activity webhooks for:
  • Creation, update, or deletion of ideas and features
  • Comment or vote changes within ideas and features

Limitations

• Only Ideas and Features are indexed; workspaces (products), product lines, releases, and individual votes/endorsements are out of scope.
• Only users with at least Viewer permissions in a workspace can have their content indexed and displayed.
• Workspace hierarchy and group-based permissions are handled, but some permission propagation logic relies on best-effort due to API limitations.
• Comments are indexed as part of the parent idea/feature, not as standalone records.
• Epics, Initiatives, and Goals are not currently supported in the standard configuration.
• No support for on-premises Aha! (cloud-only integration).
• Pagination may miss or duplicate items if underlying Aha! data changes during a crawl, but eventual consistency is expected.
• Webhook notifications for deletions are delayed (about 5 minutes).

Requirements

The Glean Aha! connector is designed for Aha! cloud deployments and relies on the Aha! REST API and webhooks. Proper configuration ensures accurate content retrieval and permission mapping.

Technical requirements

• An active Aha! cloud instance (e.g., yourdomain.aha.io).
• Your instance subdomain (the hostname before .aha.io) and confirmation that your organization’s Aha! plan includes REST API access. If you will use activity webhooks, confirm your plan supports webhooks for your edition.
• An Aha! user account with at least Viewer roles in all workspaces relevant for crawling.
• Network access to Aha!’s REST API endpoints.
• A supported integration platform version within Glean.

Credential requirements

• An Aha! API key (personal access token) tied to a user account with required permissions.
  • The API key can be generated via the Aha! web UI.
  • API keys must be stored securely and entered during Glean connector setup.
  • For webhook functionality: an Aha! user with Administrator and customization privileges is recommended, though not strictly required for basic content indexing. For more information, see Enable the integration.

Permission requirements

• Crawling and indexing require, at minimum, "Viewer" roles for all relevant workspaces or workspace lines.
• Administrator rights are needed for setting up activity webhooks covering all workspaces.
• Only users with a Viewer or higher role will have their associated content indexed and accessible in Glean.
• Permission propagation relies on Aha!'s workspace (product) and product line hierarchy. Users may inherit access to descendant workspaces.

Configuration and setup

This section describes how to install and configure the Aha! connector in Glean. Most setup happens in the Aha! admin console and the Glean admin console.

Step 1: Determine your Aha! instance name

1. Identify your instance name from your organization's Aha! URL. For example, if your URL is https://glean.aha.io/, your instance name is glean. You will need to provide this in the Glean setup screen later.

Step 2: Generate and enter an Aha! access token

Glean uses personal API keys to authenticate with your Aha! instance. Ensure you have generated an API key within the Aha! user interface before proceeding.

1. Copy your generated API token from Aha!. You will need to provide this in the Glean setup screen later.

(Optional) Step 3: Configure webhooks for Aha!

Webhooks allow Glean to capture activity updates in real time.

note

Creating an activity webhook integration requires elevated administrative permissions in Aha!. Verify your access level before continuing.

1. Follow the Aha! documentation to enable the activity webhook integration.
2. Copy the unique webhook URL generated for you in the Glean setup UI. It will follow this format: https://<your-domain>.glean.com/instance/AHA/events
3. Paste this value into the Hook URL field during the webhook configuration step in Aha!.

Add configuration details in Glean

1. In the Glean admin console, navigate to Data sources and select Add data source.
2. Select Aha!.
3. Enter a name.
4. Paste the generated API key from step 2 into the API token field.
5. Paste your Aha! instance name (the subdomain in <yourinstance>.aha.io') from step 1 in the Aha instance name field.
6. Click Save.

Upon completion, Glean will begin an initial crawl, indexing all accessible ideas and features according to the permissions of the API key holder. Webhook events will keep the index up to date with changes in Aha!.

Notes

• API rate limits apply: up to 300 requests per minute and up to 20 requests per second per source IP address.
• The updated_since parameter is used to perform incremental fetches.
• Webhook notifications typically arrive with a 5-minute delay after the triggering event.