# How to connect Brilliant Directories to OpenClaw (paste one key, 44 tools) > Connect Brilliant Directories to OpenClaw with ClawLink: paste your Brilliant Directories key once and 44 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/brilliant-directories The usual route to Brilliant Directories access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Brilliant Directories setup: install one ClawHub skill, connect Brilliant Directories in the browser, and OpenClaw can call real Brilliant Directories actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Brilliant Directories. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Brilliant Directories** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect brilliant-directories # connect Brilliant Directories (browser OAuth) npx -y @useclawlink/cli actions brilliant-directories # list available actions npx -y @useclawlink/cli run brilliant-directories --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Brilliant Directories in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Brilliant Directories API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Brilliant Directories, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Brilliant Directories is connected in the dashboard, that agent calls the same 44 Brilliant Directories tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Brilliant Directories MCP for OpenClaw Looking for a Brilliant Directories MCP server for OpenClaw? ClawLink connects Brilliant Directories to OpenClaw and exposes 44 Brilliant Directories tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Brilliant Directories integration](https://claw-link.dev/hermes/brilliant-directories) works the same way. ## What the OpenClaw Brilliant Directories integration can do 44 Brilliant Directories tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 44. ### 30 of 44 Brilliant Directories tools for OpenClaw | Tool | What it does | |---|---| | **Get album photo** `brilliant_directories_get_album_photo` | Retrieves the complete metadata and details for a single album image from Brilliant Directories | | **Get data categories** `brilliant_directories_get_data_categories` | Retrieves all available custom fields for Data Categories (Post Types) in a Brilliant | | **Get data category** `brilliant_directories_get_data_category` | Retrieve configuration data for a single post type (data category) in Brilliant Directories | | **Get data post** `brilliant_directories_get_data_post` | Retrieve a single image/video post from the Brilliant Directories member posts system | | **Get lead** `brilliant_directories_get_lead` | Retrieve a single lead's complete information from Brilliant Directories | | **Get lead fields** `brilliant_directories_get_lead_fields` | Retrieves all available fields in the leads table from a Brilliant Directories website | | **Get portfolio group** `brilliant_directories_get_portfolio_group` | Retrieve multi-image post data by group_id | | **Get review** `brilliant_directories_get_review` | Retrieve complete review data from Brilliant Directories based on review_id | | **Get reviews fields** `brilliant_directories_get_reviews_fields` | Get metadata about all available fields in the users_reviews table from a Brilliant Directories | | **Get unsubscribe** `brilliant_directories_get_unsubscribe` | Retrieve a single unsubscriber record by ID | | **Get user** `brilliant_directories_get_user` | Retrieve comprehensive data for a single user by their user_id | | **Get user fields** `brilliant_directories_get_user_fields` | Retrieves comprehensive user data from the Brilliant Directories database by searching for a | | **Get user transactions** `brilliant_directories_get_user_transactions` | Retrieves payment and transaction history for a member in Brilliant Directories | | **Get users click** `brilliant_directories_get_users_click` | Retrieve click tracking data for a single user clicked link based on the click_id | | **Get widget** `brilliant_directories_get_widget` | Retrieves the data of a single widget based on the widget_id | | **Search reviews** `brilliant_directories_search_reviews` | Search reviews and their related data from the database | | **Search users** `brilliant_directories_search_users` | Search for users/members in the Brilliant Directories database with advanced filtering options | | **Create album photo** `brilliant_directories_create_album_photo` | Add a new album photo to a user's portfolio in Brilliant Directories | | **Create data category** `brilliant_directories_create_data_category` | Creates a new data category (post type) in the Brilliant Directories website database | | **Create data post** `brilliant_directories_create_data_post` | Create a new Single Image Post (member post) in the Brilliant Directories database | | **Create lead** `brilliant_directories_create_lead` | Create a new lead in the Brilliant Directories database | | **Create portfolio group** `brilliant_directories_create_portfolio_group` | Creates a new multi-image portfolio post in the Brilliant Directories database | | **Create unsubscribe** `brilliant_directories_create_unsubscribe` | Add an unsubscriber to the database and unsubscribe a member from email campaigns | | **Create user** `brilliant_directories_create_user` | Creates a new user/member account in the Brilliant Directories website database | | **Create users click** `brilliant_directories_create_users_click` | Add a new user clicked link tracking record to the database | | **Create widget** `brilliant_directories_create_widget` | Create a new widget in the Brilliant Directories website database | | **Match leads** `brilliant_directories_match_leads` | Match a batch of emails or user IDs to a specific lead record | | **Update album photo** `brilliant_directories_update_album_photo` | Updates an existing album photo record in the Brilliant Directories database | | **Update data category** `brilliant_directories_update_data_category` | Update an existing post type (data category) record in Brilliant Directories | | **Update data post** `brilliant_directories_update_data_post` | Updates a single image post record and related data in the Brilliant Directories database | ## Example prompts **Get Album Photo** > Pull the relevant data from Brilliant Directories, summarize it in plain English, and point out anything that needs attention. **Get Data Categories** > Pull the relevant data from Brilliant Directories, summarize it in plain English, and point out anything that needs attention. **Get Data Category** > Pull the relevant data from Brilliant Directories, summarize it in plain English, and point out anything that needs attention. **Get Data Post** > Pull the relevant data from Brilliant Directories, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brilliant Directories working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Brilliant Directories API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Brilliant Directories account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Brilliant Directories. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Brilliant Directories actions to the runtime in a format your agent can reliably use. | 44 tools for Brilliant Directories are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Brilliant Directories to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Brilliant Directories in the browser, and the 44 tools above work from chat. There is no SDK and no config file, and the Brilliant Directories key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Brilliant Directories skill but can't call the tools The ClawHub skill teaches OpenClaw about Brilliant Directories, but the calls run through the ClawLink plugin and your connected account. Make sure Brilliant Directories is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Brilliant Directories from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Brilliant Directories tools Brilliant Directories tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Brilliant Directories call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Brilliant Directories returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Brilliant Directories has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Brilliant Directories integration? Yes. ClawLink is the fastest way to connect OpenClaw to Brilliant Directories: link your Brilliant Directories account once in the browser and OpenClaw can call the Brilliant Directories API through 44 ready-made tools — no custom code or token handling. ### How do I add Brilliant Directories to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Brilliant Directories skill from ClawHub, then you click Connect in the dashboard to authorize Brilliant Directories. OpenClaw calls the tools from the next message — no config files, and the Brilliant Directories key you paste is stored server-side instead of in your environment. ### How long does it take to connect Brilliant Directories to OpenClaw? About two minutes. Sign in, click Connect next to Brilliant Directories in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Brilliant Directories up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Brilliant Directories working from chat. ### OpenClaw installed the Brilliant Directories skill but can't call the tools The ClawHub skill teaches OpenClaw about Brilliant Directories, but the calls run through the ClawLink plugin and your connected account. Make sure Brilliant Directories is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.