Aha!

Aha! is where a lot of product-driven companies plan what gets built. Connecting it lets Sonora link customer feature requests to the corresponding Aha! ideas and features — so when a feature ships, the request that drove it can fire a playbook that generates an action telling you which customers asked for it.

The integration is read-only.

What syncs

• Ideas
• Features
• Releases
• The relationships between them

Each item maps to Sonora’s feature-request and roadmap views and stays linked to whichever customer-facing requests produced it.

Prerequisites

• An Aha! account with admin or product-owner access (needed to issue API keys)
• Your Aha! company subdomain — the prefix in your Aha! URL (e.g., mycompany from mycompany.aha.io)

Setup

1. Generate an Aha! API key

1. Sign in to Aha! and go to Settings → Account → API.
2. Create a new personal API key labeled “Sonora Integration”.
3. Copy the key.

2. Connect in Sonora

1. Settings → Integrations → Aha! → Connect.
2. Fill in:
   • Company Domain — your Aha! subdomain (e.g., mycompany for mycompany.aha.io)
   • API Key — the key you generated
3. Click Test Connection to verify, then save.

The initial sync pulls active ideas, features, and releases. Subsequent syncs are incremental.

Linking customer requests

After the initial sync, customer-facing feature requests detected from calls and tickets can be linked to Aha! ideas and features in the customer profile or feature-request view. When the linked item ships in Aha!, every related customer request is updated and a release-announcement action is generated for the customers who asked.

Disconnect

From Settings → Integrations, disconnect the Aha! card. To revoke at the Aha! side, delete the API key in Settings → Account → API.

Troubleshooting

“Invalid API key” — Confirm the key was copied without surrounding whitespace and that it hasn’t been rotated. Aha! invalidates personal API keys when the issuing user is removed; if your integration user changed, generate a fresh key.

“Not found” or empty results — Most often this is a wrong company domain. Use exactly the prefix of your Aha! URL, without https:// or .aha.io.