--- title: "Aha! Integration" description: "Connect AI agents to Aha!, the product roadmap platform. Agents create and update features, capture ideas, and read products, releases, and initiatives to keep roadmaps in sync with customer feedback." url: https://flowrunner.ai/integrations/aha-io date_modified: 2026-08-04T10:04:16-07:00 --- # Aha! [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Aha!, the product roadmap platform. Agents create and update features, capture ideas, and read products, releases, and initiatives to keep roadmaps in sync with customer feedback. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [Aha! website](https://aha.io/) · [Platform Documentation](https://www.aha.io/api) · Capability data verified 2026-07-28 1. A customer request is captured in the support or sales stack 2. List Products resolves which workspace owns the affected product area 3. List Ideas runs a full-text query to check whether this request already exists in the portal 4. Agent compares the new request against near-matches by name and description 5. A product manager rules on borderline duplicates, because merging two different asks under one idea silently miscounts demand for both 6. Create Idea files the request in the right product's portal with description and category 7. The submitting rep gets the idea's reference number to share with the customer ## What This Integration Enables Aha! is where product strategy is supposed to meet evidence, and the evidence arrives everywhere except Aha!: in tickets, call notes, Slack threads, and spreadsheets. This connector closes the gap with FlowRunner agents that browse products and their configuration, search and update features by reference number, capture ideas into portals with duplicate checks first, and read releases and initiatives for roadmap reporting. The stance: a roadmap is a set of commitments, and commitments should change by decision, not by automation side effect. Agents move information into and out of Aha! at machine speed; the calls that reshape the roadmap stay with product managers. What changes is the quality of those calls: a PM prioritizing against a portal where every ask actually landed is making a different, better decision than one prioritizing against the fraction of demand that survived manual filing. - File customer requests as ideas in the correct product portal - Create features from external intake with status and assignee set - Advance feature workflow status as delivery tools report progress - Search features across products for reporting and audits - Pull releases and initiatives into stakeholder-facing reports ### Without FlowRunner **Ideas leak before they reach the portal**: Requests surface in calls and tickets, get promised a write-up, and evaporate **The roadmap and the tracker disagree**: Engineering ships in Jira while Aha! still shows the feature in design **Demand counts are unreliable**: The same ask lives as four differently worded ideas, each with a quarter of the votes ### With FlowRunner **Every request lands with a reference number**: Ideas file themselves into the right product portal the day they are voiced **Shipped means shipped everywhere**: Agents advance feature status as delivery systems report, so the roadmap tracks reality **Demand consolidates**: Duplicate checks run before filing, and votes accumulate where they belong ## Use Case Scenarios ### The Jira-to-roadmap reconciliation Weekly, the agent pulls recently resolved enhancements from [Jira](https://flowrunner.ai/integrations/jira-issues), then runs List Features with a query for each to find the roadmap counterpart. Matches get Update Feature to advance workflow status; unmatched shipped work gets flagged, because something reached customers that the roadmap never tracked, and product should know that happened. The roadmap stops being a lagging indicator of its own delivery organization. ### Slack threads become countable demand Field teams drop customer asks into a requests channel. The agent reads them from [Slack](https://flowrunner.ai/integrations/slack), resolves the product with List Products, checks List Ideas for prior art, and files Create Idea with the customer context in the description and the right category. The thread gets the reference number back. Six months later, when prioritization happens, the ask has a vote trail instead of a vague memory that "a few customers wanted this". ### The stakeholder roadmap report that builds itself Before each business review, the agent walks List Releases and List Initiatives for each product, pulls feature detail with Get Feature for the flagship items, and writes the rollup to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): initiatives, their releases, feature status counts, and what shipped since last review. Product leadership edits a current document instead of assembling one, and the review discusses direction rather than reconstructing state. ## Human-in-Loop Highlight Update Feature can change a feature's workflow status, and in Aha! that status is read as a promise: the moment a feature shows as scheduled or shipped, sales quotes it, success references it, and executives report it upward. An agent syncing from delivery tools can be confidently wrong in both directions, marking shipped a feature that shipped dark behind a flag, or leaving in-design something a customer was told is out. So FlowRunner flows advance status automatically only along low-stakes transitions, and any change that moves a feature onto or off the visible roadmap stops for the product owner: "Jira epic PLAT-88 resolved. Advance PROD-123 'Bulk export' to Shipped? It appears in the Q3 launch comms." The same gate guards Create Feature from intake sources, because a feature record created carelessly is a commitment nobody made. Ideas flow freely; the roadmap changes on signature, with the approval logged next to the status it authorized. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Products 2 - **List Products** Lists the workspaces the API key can access, with ID, reference prefix, and name, paged up to 200 per page. The scoping step before every product-bound operation. - **Get Product** Retrieves one product by ID or reference prefix with name, description, and configuration. ### Features 4 - **List Features** Lists and full-text searches features across products, with filters for workflow status name and assigned user. The reconciliation and reporting read. - **Get Feature** Retrieves a feature by ID or reference number, such as PROD-123, with description, workflow status, assignee, release, tags, and custom fields. - **Create Feature** Creates a feature in a product with a name, plus optional rich-text description, initial workflow status, and assignee. Gated in FlowRunner intake flows because a feature record reads as a commitment. - **Update Feature** Partially updates a feature's name, description, workflow status, or assignee by ID or reference number. The write FlowRunner gates on roadmap-visible status transitions. ### Ideas 2 - **List Ideas** Lists a product portal's ideas with full-text query and category filters, returning reference numbers, workflow status, and vote and endorsement counts. The duplicate check before filing. - **Create Idea** Creates an idea in a product's portal with a name, plus optional description, initial workflow status, and category. The write that turns a hallway request into countable demand. ### Releases 1 - **List Releases** Lists a product's releases with reference number, name, release date, and shipped and parking-lot flags. The scheduling context for roadmap reports. ### Initiatives 1 - **List Initiatives** Lists a product's strategic initiatives with reference number, name, and status. The strategic grouping layer for rollups and reviews. ## Frequently Asked Questions ### What can FlowRunner do with Aha!? FlowRunner agents can run List Products, Get Product, and List Features in Aha!, plus 7 more actions. ### Does connecting Aha! to FlowRunner require OAuth? No. Aha! connects to FlowRunner with an API key, no OAuth flow required. ### Can Aha! trigger a FlowRunner workflow automatically? Aha! doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Aha!?** This integration exposes Aha! to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/aha-io. Site index: https://flowrunner.ai/llms.txt