How to connect Adyntel to OpenClaw
Connect Adyntel to OpenClaw with ClawLink: paste your Adyntel key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
AdyntelAPI KEYMCPAdyntel provides an API to retrieve LinkedIn ads for a given company using the company's domain or LinkedIn Page ID.. Once connected, OpenClaw can read and act on Adyntel from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Adyntel 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 Adyntel setup: install one ClawHub skill, connect Adyntel in the browser, and OpenClaw can call real Adyntel 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 Adyntel.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Adyntel
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Adyntel?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Adyntel in the ClawLink dashboard — paste your Adyntel API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Adyntel, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Adyntel is connected in the dashboard, that agent calls the same 8 Adyntel tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Adyntel MCP for OpenClaw
Looking for a Adyntel MCP server for OpenClaw? ClawLink connects Adyntel to OpenClaw and exposes 8 Adyntel tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Adyntel integration works the same way.
What the OpenClaw Adyntel integration can do
8 Adyntel tools are ready for OpenClaw once the account is connected.
All 8 Adyntel tools for OpenClaw
| Tool | What it does |
|---|---|
Get google ads by company adyntel_get_google_ads_by_company | Retrieve Google ads for a company domain |
Get google shopping search status adyntel_get_google_shopping_search_status | Check the status and retrieve results of a Google Shopping ads search |
Get linked in ads by company adyntel_get_linked_in_ads_by_company | Retrieve LinkedIn ads for a company by domain or LinkedIn page ID |
Get meta ads by company or page adyntel_get_meta_ads_by_company_or_page | Retrieve Meta/Facebook ads for a company domain or Facebook page URL |
Get paid vs organic keywords adyntel_get_paid_vs_organic_keywords | Analyze paid vs organic keyword performance for a company domain |
Meta ad search adyntel_meta_ad_search | Search the Meta ad library |
Search tik tok ads by keyword adyntel_search_tik_tok_ads_by_keyword | Search the TikTok ad library using keywords |
Start google shopping search adyntel_start_google_shopping_search | Start an asynchronous Google Shopping ads search for a company domain |
Try it: find the Adyntel tool you need
Browse the 8 Adyntel tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Adyntel, summarize it in plain English, and point out anything that needs attention.
Search Adyntel for what I need, summarize the results, and tell me the next best action.
Pull the relevant data from Adyntel, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Adyntel, 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 Adyntel working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Adyntel API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Adyntel 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 Adyntel. | 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 Adyntel actions to the runtime in a format your agent can reliably use. | 8 tools for Adyntel are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Adyntel 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 Adyntel in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Adyntel key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Adyntel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Adyntel, but the calls run through the ClawLink plugin and your connected account. Make sure Adyntel 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 Adyntel 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 Adyntel tools
Adyntel 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 Adyntel 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.
Adyntel 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 Adyntel has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Adyntel integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Adyntel: link your Adyntel account once in the browser and OpenClaw can call the Adyntel API through 8 ready-made tools — no custom code or token handling.
How do I add Adyntel to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Adyntel skill from ClawHub, then you click Connect in the dashboard to authorize Adyntel. OpenClaw calls the tools from the next message — no config files, and the Adyntel key you paste is stored server-side instead of in your environment.
How long does it take to connect Adyntel to OpenClaw?
About two minutes. Sign in, click Connect next to Adyntel in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Adyntel 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 Adyntel working from chat.
OpenClaw installed the Adyntel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Adyntel, but the calls run through the ClawLink plugin and your connected account. Make sure Adyntel 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.
