Integrations & API

Integrations

Every tool Rixe connects to, what each connection is used for and how to set it up.

Integrations connect Rixe to the tools you already use: Google for search and analytics data, your CMS for publishing, your web server or CDN for AI crawler visits, your store for revenue, and project tools for turning actions into tasks. This page lists every connection and how it is set up. For building your own integration, see the REST API, webhooks and the MCP server.

Where to find it

Open the user menu at the bottom of the sidebar and choose Connections. The page shows one card per app with a status badge:

BadgeMeaning
connectedWorking and syncing.
not connectedNot set up yet.
needs an API keyThe connection needs a key from you.
readyNothing to connect; the feature works as soon as you use it.
expired / errorThe last attempt failed or the authorisation ran out. Open the card and reconnect.

Click a card to open its page, which has the step-by-step instructions and the connect control.

Search and analytics

ConnectionWhat it is used forHow to connect
Google Search ConsoleClicks and impressions per page, for AI traffic and impact measurement.Click Connect, sign in with Google and keep every requested permission ticked.
Google Analytics 4AI-referred sessions and conversions.Comes with the same Google connection.
Bing WebmasterBing verification, IndexNow and sitemap readiness.No key needed. Run the Bing readiness package on the Site Health page; published content is then announced to Bing via IndexNow automatically.

The Google connection asks for read access to Search Console and Analytics, plus your Business Profile. Nothing in your Google account is changed without your approval. Search Console data appears under LLM Analytics › Search Console. See AI traffic and crawlers.

Publishing (CMS)

CMS publishing sends approved content straight to your site as drafts or published pages. It supports WordPress, Shopify, GitHub, Webflow, Ghost, Strapi, Sanity, Storyblok, Contentful and HubSpot; for Framer, ideasoft, ticimax and ikas it prepares a package for you to upload. Connections are managed on the Publishing page (reach it from the CMS card or with ⌘K). You can revoke a connection at any time.

For WordPress, the Rixe plugin can connect itself: click Connect to Rixe in the plugin, and approve the connection in Rixe. Nothing is saved until your site answers Rixe's verification call, so nobody can connect a site they do not control.

Every published page can send a content-published webhook. See Content.

AI crawler logs

These connections tell Rixe which AI bots (GPTBot, PerplexityBot, ClaudeBot and others) visit your site. Pick the one that matches your hosting:

SourceHow it sends visits
CloudflarePaste one read-only API token; Rixe pulls the AI-bot visits for you.
VercelVercel Log Drains to the drain URL shown on the card, with the token as a bearer header. Log Drains need a Vercel Pro or Enterprise plan.
NetlifyNetlify Log Drains or an Edge Function.
FastlyFastly real-time log streaming.
Your own serverOne command streams your nginx or Apache access log to the drain URL.
WordPressThe Rixe WordPress plugin; once approved, bot traffic flows with no token.

The card for each source generates the token and shows the exact drain URL. See AI traffic and crawlers.

Store revenue

ConnectionWhat you need
ShopifyA custom app with the read_orders Admin API scope; paste your myshopify.com domain and the Admin API access token.
ikasAn API access token with permission to read orders; paste your store name and the token.
WooCommerceA REST API key pair with Read permission only; paste the store address (with https://) and both keys.

Orders are pulled every night and AI channel revenue is calculated from them; WooCommerce also feeds your product list. Keys are tested against your store before they are saved, and stored encrypted. See E-commerce.

Sending and notifications

ConnectionWhat it does
Gmail (sending)Sends autopilot outreach e-mails from your Gmail account. Only send permission is requested; your inbox is never read.
SlackPaste a Slack Incoming Webhook URL; alerts post to that channel. Which alerts go to Slack is set in Settings › Notifications.

See Alerts and inbox and Sources, outreach and PR.

SEO data and project tools

These connect with an API key from your own account in that tool: create the key there, paste it into the form on the card, click Save, then test the connection.

ConnectionWhat it is used for
SemrushKeyword volume and difficulty, Authority Score.
AhrefsKeyword volume and difficulty, Domain Rating.
MozDomain Authority (Links API).
AirtableWrites findings and drafts as rows in a table.
NotionWrites pages into a database.
AsanaOpens tasks in a project.
ClickUpOpens tasks in a list.
LinearOpens issues in a team.
SalesforceOpens tasks in Salesforce.
Google DocsCreates documents through the Google connection (needs the Docs permission).

Developer connections

ConnectionWhere to set it up
Data APIRead-only endpoints for Looker Studio, Power BI and warehouses. See REST API and Looker Studio.
WebhooksSigned POSTs on significant change, audit, publish and workflow events. See Webhooks.
MCP (Claude / Cursor)Use Rixe as a tool inside an AI assistant. See MCP server.
Zapier / MakeWebhooks plus an API key; no custom app needed.

All four are managed in Settings › Developer. The Data API and MCP need a plan with API access; the other integrations on this page are available on every plan. See Plans and limits.

Common questions

Who can create API keys and webhooks? Owners and admins. See Team and roles.

A card says "error". What now? Open it: the page shows the last error. Most of the time the token was revoked or expired on the other side; reconnecting fixes it. Rixe never drops data silently; a broken connection is shown as broken.

Does Rixe change anything in my Google account or store? No. Google, store and crawler connections only read. Only CMS publishing, Gmail sending and the project tools write anything, and only what you approve.

Still stuck? Write to [email protected] and a person will answer.