Integrations overview
How connections work: where they live, who can add one, what they power, and what they cost.
On this page
What a connection is
A connection is a credential you store once — an API key for one of the apps in the catalogue, a CMS publish target, or a Google account. Once it's stored, anything in that workspace can use it without you pasting it again.
Where they live
The workspace's Integrations tab is the hub: Google Search Console and Google Analytics 4 under Data sources, the full connector catalogue under Browse, whatever you've connected in between, and your own custom API keys at the bottom.
Two forms live elsewhere for good reasons: publish targets are also reachable from a grid's Publish column, and the Google Docs connection is set up from a grid's Google Doc column. Settings → Integrations holds no forms at all — it's a directory that links you into each workspace.
Connections belong to a workspace
Every connection is stored per workspace, never per organization. An agency connecting a client's Webflow connects it on that client's workspace, and connects it again for the next one. That's deliberate: each client's accounts stay theirs.
OAuth or a pasted key
Three connections use Google sign-in: Search Console, Analytics 4, and Google Docs. Everything else is a pasted API key — including Slack, Notion, HubSpot and Webflow, which people often assume are OAuth. You create the key in the other product and paste it in.
Most connections offer Test & save, which calls the service before storing the key. Some can't be tested because the host is part of each step's own config (a self-hosted Strapi, a Shopify store subdomain, a Sanity dataset) — those save unverified and fail on first use if the key is wrong.
Who can connect what
- API key connections — an admin, strategist or writer. Viewers can't.
- Publish targets (WordPress, Webflow, Ghost, Sanity, webhook) — a workspace admin only.
- Google connections — anyone with write access.
So a strategist can add an Ahrefs key but cannot connect a WordPress site. Everyone can see the list of what's connected; nobody can read a stored secret back.
What a connection powers
- Workflows — the Connector step reaches every app in the catalogue and every operation it declares.
- Nova — can list what's connected and call any operation on a connected app, and will point you at the Integrations tab when something isn't connected.
- Grids — indirectly. A grid's own columns cover publishing, Google Docs and Search Console metrics; to reach anything else, a grid runs a saved workflow through its Workflow column.
What it costs
A connector step is one task, the same for every app in the catalogue — the price is per step, not per service. A connector call made by Nova is billed as part of that Nova turn instead.
Mentionova fronts no key for any of these: every connection is your own credential, and your Ahrefs or Semrush quota is spent against your own account.
How secrets are handled
Keys are encrypted at rest, decrypted only at run time, and never returned by any read — they don't appear in run inputs, the debug view, or a workflow export. A step refers to one as {{connections.name}}, and that prefix is reserved: an unknown name is left in place so the step fails loudly rather than sending an empty credential.