Resources · Make integration

Aha! Make integrationAutomate Aha! with Make.

What could your roadmap do on its own if every new feature or idea moved where it needs to go? The Aha! Make integration gives you 16 modules: 2 instant triggers, 13 actions and 1 search. This page shows product teams how to connect the account and build a first working scenario.

Try the Aha! integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Aha! Make integration automate?

The Aha! Make integration links your Aha! account to Make, a visual tool where you build a scenario (the automation itself, a chain of steps) without writing code. Each step is a module: something that listens to Aha!, reads a record, or changes one. Aha! can then react to other apps, and other apps can react to Aha!.

Ideas that arrive from anywhere. A request lands in a form, a support tool or a shared sheet, and Create an Idea files it in Aha! so product managers review it with the rest, instead of copying it by hand.

A roadmap that tells people when it moves. Watch New Feature fires the moment someone adds a feature, and Watch New Activity follows what happens in the account. Both are instant: Aha! calls Make through a webhook, so the next app hears about it without waiting for a schedule.

A tidy portal audience. With Search Portal Users, Create a Portal User and Update a Portal User, the list of people allowed into your portal follows the customer list you keep elsewhere.

What the modules do not cover yet, Make an API Call can reach, with the same connection. The Make documentation for this app is marked as AI-generated from the Aha! docs, so check any detail that matters in Aha! itself. The same app often has an n8n node too: the n8n vs Make comparison lays out the differences, and the Make pricing page explains what the plans include.

Connect

How do you connect your Aha! account to Make?

  1. 01

    Generate an API key in Aha!

    In Aha!, open the Settings menu, click API keys, then use the button that generates a new key. Copy it right away: it is what lets Make act on your account. You need an active Aha! account for this.

  2. 02

    Add an Aha! module and open the connection

    In your Make scenario, add any Aha! module and click Create a connection. A connection is your Aha! account linked to Make once, then reused by every Aha! module. The Connection name field is optional; a clear name helps if you manage several workspaces.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen if you authenticate with an OAuth2 token instead. Save, and the module can now list what it reads from your Aha! account.

First scenario

Your first scenario: turn incoming requests into Aha! ideas

GoalWhen a request arrives in another app, Make files it in Aha! as a new idea.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module: the app where requests come in, such as your form tool or help desk.

  2. 02

    Add Create an Idea

    Click the + on the right of that first module, search for Aha! and pick Create an Idea. Choose your Aha! connection, or create it with the API key from the steps above.

  3. 03

    Map the request into the idea

    Fill the module fields by mapping the request text from the first module. Once the connection exists, Make lists the Aha! objects it can read, so you pick the target instead of typing it.

  4. 04

    Test with Run once

    Send one sample request, then click Run once. Read the bundle each module received (one bundle is one item, here one request) and check the idea in Aha!.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What can start an Aha! scenario?

2 modules start a scenario when something happens in Aha!. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Aha! as soon as it happens.

Aha!1Watch New Activity

Watch New Activity

Instant trigger

In Make“Triggers when there is new activity.”

This trigger starts your scenario whenever something new happens in your Aha! account, so the rest of your tools can follow the life of the roadmap without anyone reposting updates by hand.

How it fires
instant, Aha! calls Make through a webhook as soon as the activity happens, with no schedule to wait for.
When to use it
when a team channel or a log sheet should hear about changes in Aha! as they occur, rather than being tied to one type of record.
Watch out
click Create a webhook before the connection, and use Run once on a real change to see which details the bundle carries.
Aha!2Watch New Feature

Watch New Feature

Instant trigger

In Make“Triggers when a new feature is created.”

Watch New Feature hands you each feature the moment it is created in Aha!, ready to share with the teams that build, sell or support it.

How it fires
instant, Aha! calls Make through a webhook as soon as the feature exists, so the scenario does not poll on a clock.
When to use it
when engineering needs a ticket or sales needs a heads-up every time a feature joins a release.
Watch out
it reacts to new features only; if later edits matter, combine it with Watch New Activity or read the record again with Get a Feature.
Modules

What can Make do in Aha!?

Aha! gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Aha!1

Create a Feature

Action

In Make“Creates a new feature for a release.”

Adds a feature to a release in Aha!, so work agreed somewhere else shows up on the roadmap without being typed twice.

When to use it
when a request approved in another tool should become planned work in a specific release.
Watch out
run it once on a test release first, then check where the feature landed before switching the scenario on.
Aha!2

Create an Idea

Action

In Make“Creates a new idea.”

Files a new idea in Aha!, giving customer requests and team suggestions one place to be reviewed and ranked.

When to use it
when feedback reaches you through a form, an inbox or a support tool and should join the ideas already collected.
Watch out
every run creates a fresh idea, so a request sent twice lands twice unless the first module filters duplicates.
Aha!3

Create a Portal User

Action

In Make“Creates a new portal user.”

Gives a person access to your Aha! portal by creating their portal user, which saves an admin from inviting each new customer by hand.

When to use it
when a customer signs up or becomes active in your CRM and should be able to post and follow ideas.
Watch out
put Search Portal Users before it, so someone already registered is not created a second time.
Aha!4

Delete a Feature

Action

In Make“Deletes a feature specified by ID.”

Removes a feature from Aha! by its ID, which keeps the roadmap clean when the work behind it is cancelled in another system.

When to use it
when a project is dropped in your delivery tool and the matching feature should disappear from Aha! too.
Watch out
removing is the whole job of this module, so test on a throwaway feature with Run once before pointing it at real data.
Aha!5

Delete an Idea

Action

In Make“Deletes idea specified by ID.”

Deletes one idea by its ID, useful to clear out test entries or submissions your intake scenario should never have filed.

When to use it
when a filter step flags a submission as spam or as a test and you want it gone from the ideas list.
Watch out
map the ID from a module that just found or created that exact idea, never a typed value reused across runs.
Aha!6

Delete a Portal User

Action

In Make“Deletes a portal user specified by ID.”

Closes portal access for one person by deleting their portal user, so former customers stop seeing your ideas portal.

When to use it
when an account is cancelled in your billing or CRM tool and access should end with it.
Watch out
the module needs the portal user ID; get it with Search Portal Users first, then check the match before deleting.
Aha!7

Get a Feature

Action

In Make“Gets a feature specified by ID.”

Reads one feature by its ID and hands its full details to the next module, so you can pass them on accurately.

When to use it
after Watch New Feature or Watch New Activity, when the trigger gives you an ID and the following app needs the whole record.
Watch out
it reads a single feature; without an ID from an earlier step it has nothing to fetch.
Aha!8

Get an Idea

Action

In Make“Gets idea specified by ID.”

Returns one Aha! idea by its ID, so a scenario can check where a request stands before acting on it.

When to use it
when a customer asks about a request in your help desk and the reply should reflect what the idea says today.
Watch out
keep the idea ID somewhere when the idea is created, in a sheet or a CRM field, or you will have nothing to look it up with.
Aha!9

Get a Portal User

Action

In Make“Gets a portal user specified by ID.”

Pulls the record of one portal user by ID, handy when another app needs to know who is behind a portal account.

When to use it
when an ID comes out of an earlier Aha! step and you want the person's details before writing them to your CRM.
Watch out
without an ID, start with Search Portal Users, which returns the matching portal users.
Aha!10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Aha! API with the connection you already set up, for the jobs the ready-made modules do not offer.

When to use it
when the operation you need is in the Aha! API but not in this list of 16 modules.
Watch out
this module expects you to read the Aha! API documentation and build the request yourself; the other modules spare you that work.
Aha!11

Update a Feature

Action

In Make“Updates feature specified by ID.”

Changes an existing feature, found by its ID, so the roadmap reflects what the delivery team reports.

When to use it
when the status of the matching work changes in your ticketing tool and the feature in Aha! should follow.
Watch out
fill only what should change, then use Run once to compare the feature before and after on a test record.
Aha!12

Update an Idea

Action

In Make“Updates an idea specified by ID.”

Edits an idea already in Aha!, by ID, so details added later by a customer or a colleague are not lost.

When to use it
when a support conversation brings new context about a request that already exists as an idea.
Watch out
the scenario must know which idea to touch, so store the ID when the idea is filed or fetch it with Get an Idea.
Aha!13

Update a Portal User

Action

In Make“Updates a portal user specified by ID.”

Keeps a portal user's record in line with your source of truth by editing it through its ID.

When to use it
when a customer's details change in your CRM and their portal profile should say the same.
Watch out
chain it after Search Portal Users so the right person is edited, and add a filter for the case where no one is found.
Aha!14

Search Portal Users

Search

In Make“Searches for portal users.”

Looks up portal users and returns every match, which is how you find the ID the Get, Update and Delete modules ask for.

When to use it
before creating a portal user, to check whether the person is already registered.
Watch out
a search can return zero, one or several bundles, and each bundle sent to the next module costs an operation, so filter what comes out.
Need help

Need help automating Aha! with Make?

A person reads every message.

FAQ

Aha! and Make: common questions

01Is the Aha! Make integration free?
Yes, on the Make side. Aha! is a standard app, so it works on the Free plan, which allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Scheduled runs on Free are spaced at least 15 minutes apart; paid plans (Core, Pro, Teams and Enterprise) go down to 1 minute, with unlimited active scenarios. Make counts usage in operations, one per module run on one bundle. You still need your own active Aha! subscription, which Make does not provide.
02What do you need to connect Aha! to Make?
An active Aha! account and either an API key or an OAuth2 token. To get the key, open the Settings menu in Aha!, click API keys and generate a new one, then copy it. In Make, add an Aha! module, click Create a connection, give it a name if you like, and paste the key or follow the on-screen steps. For the two instant triggers, create the webhook first and the connection right after. The connection is then reused by every Aha! module in your scenarios.
03Do the Aha! triggers in Make react in real time?
Yes. Both Aha! triggers, Watch New Activity and Watch New Feature, are instant: Aha! calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. In the editor they carry the lightning badge. That is why setting them up starts with Create a webhook before the connection. Scenarios that begin with another app, like the intake example on this page, run on the schedule of their first module, every 15 minutes by default.
04What if an Aha! module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Aha! API through the connection you already have, so you can reach what the 13 actions and the single search do not cover, provided you are comfortable reading the Aha! API documentation. Keep in mind that the Make documentation for this app is labeled as AI-generated from the Aha! docs and may contain mistakes; when a detail matters, verify it with Aha! before relying on it in a live scenario.
05Should you pick Make or n8n for Aha!?
It depends on where your automations already live. The same app often has an n8n node as well, so check what each tool offers for Aha! before choosing. In Make you get 16 ready-made modules, including instant triggers for new features and new activity, plus Make an API Call for the rest, all in a visual editor you test with Run once. If your team already runs its scenarios in Make, keeping Aha! there means one connection and one place to maintain everything.
Same platform

Other docs you might need on this stack.

Browse all integrations