How to connect Datagma to OpenClaw
Connect Datagma to OpenClaw with ClawLink: paste your Datagma key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
DatagmaAPI KEYMCPDatagma delivers data intelligence and analytics, assisting companies in discovering market insights, tracking competitive metrics, and strategizing growth opportunities.. Once connected, OpenClaw can read and act on Datagma from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Datagma 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 Datagma setup: install one ClawHub skill, connect Datagma in the browser, and OpenClaw can call real Datagma 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 Datagma.
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 Datagma
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Datagma?"
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 Datagma in the ClawLink dashboard — paste your Datagma API key once.
Verify the connection by asking OpenClaw:
Use Datagma to detect job change and walk me through the result in plain English.
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 Datagma is connected in the dashboard, that agent calls the same 8 Datagma tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Datagma MCP for OpenClaw
Looking for a Datagma MCP server for OpenClaw? ClawLink connects Datagma to OpenClaw and exposes 8 Datagma tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Datagma integration works the same way.
What the OpenClaw Datagma integration can do
8 Datagma tools are ready for OpenClaw once the account is connected.
All 8 Datagma tools for OpenClaw
| Tool | What it does |
|---|---|
Detect job change datagma_detect_job_change | Detect if a contact changed jobs |
Enrich person or company datagma_enrich_person_or_company | Enrich person or company data using LinkedIn URLs, emails, domains, or names |
Find work email datagma_find_work_email | Find verified work email address for a person using their name and company |
Get credits datagma_get_credits | Get the current credit balance for the authenticated Datagma API account |
Get twitter by email datagma_get_twitter_by_email | Retrieve Twitter account information associated with an email address |
Get twitter by username datagma_get_twitter_by_username | Enrich Twitter profile data using Datagma's database |
Reverse phone lookup datagma_reverse_phone_lookup | Reverse-lookup information associated with a phone number |
Search phone numbers datagma_search_phone_numbers | Find mobile phone numbers using email address and/or LinkedIn profile URL |
Try it: find the Datagma tool you need
Browse the 8 Datagma tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Datagma to detect job change and walk me through the result in plain English.
Use Datagma to enrich person or company and walk me through the result in plain English.
Use Datagma to find work email and walk me through the result in plain English.
Pull the relevant data from Datagma, 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 Datagma working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Datagma API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Datagma 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 Datagma. | 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 Datagma actions to the runtime in a format your agent can reliably use. | 8 tools for Datagma are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Datagma 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 Datagma in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Datagma 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 Datagma skill but can't call the tools
The ClawHub skill teaches OpenClaw about Datagma, but the calls run through the ClawLink plugin and your connected account. Make sure Datagma 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 Datagma 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 Datagma tools
Datagma 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 Datagma 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.
Datagma 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 Datagma 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 Datagma integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Datagma: link your Datagma account once in the browser and OpenClaw can call the Datagma API through 8 ready-made tools — no custom code or token handling.
How do I add Datagma to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Datagma skill from ClawHub, then you click Connect in the dashboard to authorize Datagma. OpenClaw calls the tools from the next message — no config files, and the Datagma key you paste is stored server-side instead of in your environment.
How long does it take to connect Datagma to OpenClaw?
About two minutes. Sign in, click Connect next to Datagma in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Datagma 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 Datagma working from chat.
OpenClaw installed the Datagma skill but can't call the tools
The ClawHub skill teaches OpenClaw about Datagma, but the calls run through the ClawLink plugin and your connected account. Make sure Datagma 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.
