Make Integration Overview
The Rankwise Make app brings your AI-visibility data into Make scenarios. It reads data from the Rankwise public API. It does not write anything to your Rankwise account.
What It Does
| Module | Type | What it returns |
|---|---|---|
| Watch citations won | Trigger | An AI engine started citing you for a tracked question. Optional domain filter. |
| Watch visibility events | Trigger | Any visibility event: won, lost, fixes proposed, goal reached, autopilot paused, competitor overtake. |
| Get a domain score | Action | A domain's citation rate, per-engine rates and per-dimension scores. |
| List dimension scores | Search | One bundle per dimension, with its top fix. |
| Make an API call | Universal | The raw response from any GET /api/v1/... endpoint the other modules do not cover. |
Both triggers poll Rankwise for new events. Each event runs a scenario once.
Example Scenarios
- Watch citations won to Slack: post a message when an AI engine starts citing you.
- Watch visibility events to Google Sheets: log every won and lost citation as a row.
- List dimension scores with a Make data store: compare each score to the last stored value and route on a change.
How It Works
- Create an API key in Rankwise under Settings, then API. The key is shown once.
- Add a Rankwise connection in Make and paste the key.
- Pick a module from the table above.
- Add the next modules in your scenario and turn it on.
One API key reads one workspace. Agencies create one key per client workspace.
Limits
- There is no trigger for a dimension score change. Use List dimension scores with a data store, as in the example above.
- The app does not return the dashboard's single composite score.
- You type the domain as Rankwise shows it, for example
example.com. A domain the workspace does not track returns an error. Add an error handler route if the scenario should continue.
Coming Soon
This integration is built and waiting for Make's review. Join the waitlist to be notified when it launches.