Skip to main content

Open in AthenaHQ

app.athenahq.ai/settings/integrations

​
Purpose

The Integrations page allows customers to connect, configure, and manage third-party tools that work alongside Athena. By connecting these platforms, customers can pull in traffic and keyword data to measure their search impact, automatically publish AI-generated content directly to their CMS, and route automated reports or answers to their team’s communication tools. This page acts as the central hub for all external connections tied to the customer’s currently active website, with the exception of the Slack bot, which is configured organization-wide.

​
What’s on the page

Depending on the user’s plan and permissions, they may see a few different banners at the top of the page:
  • View-only banner: A floating pill at the bottom of the screen indicating that the user lacks write access for integrations. They can view connection statuses but cannot make changes.
  • Shopify app-install banner: If the user is returning from installing Athena in the Shopify App Store, a banner asks them to “Finish connecting Shopify” with a button to confirm the website.
The main page is divided into three collapsible sections. If an integration is connected, it sorts to the beginning of its respective section. Measure & attribute Tools for tracking website traffic, search impressions, and keyword performance.
  • Google Analytics 4: Attributes AI Search traffic, revenue, and conversions.
  • Google Search Console: Monitors branded search impressions and clicks.
  • Google Ads: Imports keyword data for smarter prompt generation.
Reporting & collaboration Tools for delivering data and insights to the customer’s team.
  • Looker Studio: Instructions for connecting Athena data to custom dashboards.
  • Slack reports: Configures weekly report delivery to Slack channels or DMs.
  • Slack bot: An organization-wide tool (Enterprise plans only) that answers customer product questions directly in Slack channels.
Integration Drawers (Drilldowns) Clicking any tile opens a side drawer tailored to that platform:
  • Disconnected state: Shows requirements, a connect form (API keys, space IDs, site URLs), or a button to open an OAuth popup (Google, Slack, WordPress.com).
  • Connected state: Displays the active account/property, related metadata (like synced CMS categories, content types, or collections), and actions to change settings or disconnect.
  • Looker Studio: This tile is unique, it does not connect directly via a button. Instead, it opens a static instructions drawer explaining how to configure Looker Studio using Athena’s data connector.

​
What you can do here

  • Connect via OAuth: For Google tools, Slack, and WordPress.com, clicking the connect button opens a secure authorization popup. Once authorized, the user selects their specific property or account from a dropdown to finalize the link.
  • Connect via API Credentials: For tools like Webflow, Wix, Sanity, Contentful, Framer, and Payload, the user enters their credentials (API keys, space/project IDs, site URLs) into the drawer’s form. The drawer often includes a “Step-by-step instructions” section explaining exactly where to find these in the third-party tool.
  • Switch Properties or Accounts: If a user is connected to Google Analytics, Search Console, or Google Ads, they can use the dropdown in the drawer to switch the active property/customer account without having to re-authenticate.
  • Sync CMS Data: Inside connected CMS drawers, users can click the refresh icon (tooltip: “Sync collections”, “Sync content types”, etc.) to manually pull in their latest CMS categories, document types, or collections. This ensures Athena knows where it can publish content.
  • Update Credentials: CMS integrations allow users to click “Update credentials” to securely rotate their API tokens or change their target server URL without severing existing published content links.
  • Manage Slack Bot Channels: Inside the Slack bot drawer, users can use a multi-select picker to add tracked channels (which auto-joins public channels), or manually add private shared channels by pasting a channel ID. Once added, users can toggle individual channels as “Enabled” or “Disabled”, or click “Remove” to stop tracking them.
  • Disconnect an Integration: Every active drawer has a “Disconnect” button. Clicking it asks for confirmation (e.g., “Confirm disconnect”). This is a destructive action that removes the credentials and clears any linked content schedules.

​
Data shown

The page displays connection statuses derived directly from Athena’s database of securely stored credentials. When a drawer is opened, Athena makes live, real-time requests to the respective third-party API (e.g., Google, Shopify, Webflow) to fetch available properties, verify token validity, and display synced CMS structures like blog categories or available fields.

​
Common workflows

Connecting Google Analytics 4
  1. Click the Google Analytics 4 tile under “Measure & attribute”.
  2. Click Connect Google Analytics inside the drawer.
  3. A Google popup appears. The user signs in and grants permissions.
  4. Once the popup closes, the drawer displays a list of available GA4 properties.
  5. Select the correct property from the dropdown. The tile now reads “Connected”.
Connecting a CMS (e.g., WordPress)
  1. Click the WordPress tile under “Create & publish”.
  2. Enter the website’s URL and click Detect connection method.
  3. Athena checks if the site uses Jetpack/WordPress.com (which requires OAuth) or standard self-hosted WordPress (which requires an Application Password).
  4. Follow the resulting prompt: either click Connect with OAuth or enter a Username and Application Password, then click Connect.
  5. The drawer updates to show the site’s details and synced blog categories.
Managing Slack Bot channels
  1. Click the Slack bot tile (requires organization member access).
  2. If unconnected, click Connect Slack and authorize the workspace.
  3. Under “Add channels”, search and select the desired channels, then click Add channel(s).
  4. The channels appear in the “Tracked channels” list below, where they can be toggled on/off or removed.

​
Empty, loading, and error states

  • Empty (No Website): If the user hasn’t selected a website in their workspace switcher, the page displays a simple box: “Select a website to manage integrations.”
  • Loading: While checking permissions and connection statuses, the page displays a skeleton outline of the 3-section grid with grey placeholder tiles.
  • Page-level Error: If the entire integrations system fails to load, a box appears reading, “Something went wrong. The Integrations page failed to load…” with “Try again” and “Reload” buttons.
  • Panel/Tile Error: If a specific drawer fails to load, it displays, “We couldn’t load this integration panel. Refresh the page or try again.” If a tile fails its background status check, it shows a red “Couldn’t load status” message directly on the card.
  • Linked from: The Settings sidebar nav (Integrations tab), deep links that automatically open specific drawers (e.g., ?provider=ga4), or redirects from the Shopify App Store.
  • Links to: External OAuth authorization popups (Google, Slack, WordPress), third-party dashboards (e.g., “Open in Webflow”, “Open Google Analytics”), and the Athena subscription upgrade dialog (if the user is on a free plan).

​
Common support questions

Why does the page tell me to upgrade my plan? Integrations are a paid feature. If an organization is on the Free plan, attempting to access this page will show a lock screen indicating that Integrations require a paid plan, along with a “View plans” button. Why is the Slack Bot tile disabled for me? The Slack Bot is an organization-wide integration, whereas most other integrations are website-specific. If a user is an external member who was only invited to a specific website (not the parent organization), they will see a message stating, “Only organization members can manage org-wide integrations.” Why did my WordPress connection say “Popup blocked” or “Timed out”? When trying to use WordPress OAuth, the browser might block the authorization window, or the customer’s server might be blocking external connections to their xmlrpc.php file. If OAuth continually times out, they can click “Use an application password instead” to try the manual credential method. I see a “View-only” banner at the bottom. How do I connect tools? The user lacks the “Integrations: Write” permission for that website. They can click tiles to see what is currently connected, but all buttons to add, modify, or disconnect tools will be disabled. They must ask an organization administrator to update their role.