Apps Marketplace
What the Marketplace is, how apps connect, and how a connection's lifecycle works
Apps > Marketplace in the RevKeen dashboard is where you connect RevKeen to the tools you already use. This page explains what the Marketplace is, how the pieces fit together, and what happens to a connection after you install an app.
- The difference between apps, first-party modules, and add-ons
- How an app connects and which connection methods exist
- What each Marketplace status means for installing
- How a connection changes over its lifecycle
- Where to go once an app is connected
What the Marketplace is for
The Marketplace is the installation point for integrations: third-party tools like Slack, Linear, HubSpot, and PracticeHub, plus first-party RevKeen modules. One check runs every decision — an app must be Available (or Beta) before it can be connected. In development and Coming soon entries are not installable.
Apps, modules, and add-ons
Three kinds of item appear in Marketplace terms. They are not the same thing:
| Kind | What it is | Examples |
|---|---|---|
| App | A third-party tool connected to RevKeen | Slack, Linear, HubSpot, PracticeHub, Quaderno |
| First-party module | A built-in RevKeen capability, enabled rather than connected | RevKeen Terminal, RevKeen Messaging, RevKeen Cart, Customer Intelligence |
| Add-on | A separately priced capability on top of your plan | Assistant, Quaderno VAT, RevKeen Cart, Customer Intelligence |
An app gives you a connection to an external tool. A module is part of RevKeen. An add-on is a billing line. The same product can appear in more than one column — RevKeen Cart, for example, is both a first-party module and a priced add-on.
How an app connects
Each app connects one of a few standard ways, shown on its Marketplace card and app page:
| Connection method | How it works | Typical apps |
|---|---|---|
| OAuth | You authorise in the provider's pop-up window | Slack, Linear, HubSpot |
| API key | You paste a credential supplied by the provider | PracticeHub, TeamUp, Wodify |
| M2M token | Machine-to-machine credentials for server apps | Developer connections |
| Device pairing | A physical device joins the workspace | RevKeen Terminal (PAX) |
| Built in | No external connection; a RevKeen module | Messaging, Cart |
Connect from Apps > Marketplace, open the app page, and follow How to activate for that specific app. The steps for every app are listed in Connecting each app.
What the statuses mean
Availability comes from the product catalog, not the app page:
| Marketplace card | Can you connect it? |
|---|---|
| Available | Yes |
| Beta | Yes, with the caveats on the app page |
| In development | No |
| Coming soon | No |
The status pill on your installed apps is a different signal: Connected, Needs attention, Reconnect needed, Failed, Not connected, Status unknown. Do not read a wiki page or the catalog as proof a live connection exists — the status pill reflects the actual connection.
The connection lifecycle
A connection starts when you install an app and follows an ordinary lifecycle:
- Browse the Marketplace and open the app you already use.
- Connect (or Enable / Set up for modules) and complete the activation steps.
- The app page confirms the status: Connected.
- Over time a connection can degrade: a provider revokes the authorisation (Reconnect needed) or a sync or health check reports a problem (Needs attention).
- You Manage the app to test, rotate credentials, or Disconnect it.
A connected app stays connected even if connection health cannot be refreshed. If health data is unavailable, Marketplace still shows the recorded or last-known status and flags Couldn't refresh connection health separately.
Daily management
Use the Installed Apps list in Marketplace to see every connection you have made and act on it:
| Lifecycle moment | What to do |
|---|---|
| Everything is healthy | Nothing. Check back when a pill changes. |
| Needs attention | Open the app page and fix the reported problem. |
| Reconnect needed | Re-authorise from the app page before it affects workflows. |
| Failed | Reconnect or disconnect, depending on whether you still need the app. |
| No longer used | Disconnect from the app page. |
Rotating or revoking a provider credential does not silently replace the connection — Reconnect is shown when the authorisation is expired or revoked, and you must complete it explicitly.
What is not live
The Marketplace is honest about unfinished work. Do not plan around entries that are not installable:
- Xero / QuickBooks invoice sync -- catalog status in development; setup screens implying live AR sync are wrong.
- TeamUp and Wodify install -- announced, not installable.
- Pay by Bank collection -- not a live checkout rail.
Related
- Integrations -- the full catalog and its statuses
- Connecting each app -- step-by-step connection for every app
- Webhooks -- custom event notifications
- Payment gateways -- processor configuration
- Ask RevKeen and Agent Studio -- how connected apps give the Assistant context