# How to connect Data247 to OpenClaw (paste one key, 24 tools) > Connect Data247 to OpenClaw with ClawLink: paste your Data247 key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/data247 The usual route to Data247 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 Data247 setup: install one ClawHub skill, connect Data247 in the browser, and OpenClaw can call real Data247 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 Data247. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Data247** — 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 data247 # connect Data247 (browser OAuth) npx -y @useclawlink/cli actions data247 # list available actions npx -y @useclawlink/cli run data247 --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 Data247 in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Data247 API key once. Verify the connection by asking OpenClaw: > Use Data247 to append email2 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Data247 is connected in the dashboard, that agent calls the same 24 Data247 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). ## Data247 MCP for OpenClaw Looking for a Data247 MCP server for OpenClaw? ClawLink connects Data247 to OpenClaw and exposes 24 Data247 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 Data247 integration](https://claw-link.dev/hermes/data247) works the same way. ## What the OpenClaw Data247 integration can do 24 Data247 tools are ready for OpenClaw once the account is connected. ### All 24 Data247 tools for OpenClaw | Tool | What it does | |---|---| | **Append email2** `data247_append_email2` | Find email addresses associated with name and postal address using Append247 service | | **Append gender** `data247_append_gender` | Determine a person's probable gender based on their first (given) name | | **Append name** `data247_append_name` | Get CNAM (Caller Name Delivery) data for a phone number | | **Append phone** `data247_append_phone` | Append phone numbers to contact records using name and address | | **Append profile** `data247_append_profile` | Retrieve comprehensive consumer profile data including identity, contact information | | **Append property data** `data247_append_property_data` | Retrieve comprehensive property data including home stats, ownership information, financials | | **Append reverse email** `data247_append_reverse_email` | Perform reverse email lookup and retrieve contact information | | **Append reverse phone** `data247_append_reverse_phone` | Perform reverse phone lookup and retrieve name and address information | | **Append reverse zipcode** `data247_append_reverse_zipcode` | Get formatted address components from a zipcode | | **Append zipcode2** `data247_append_zipcode2` | Lookup zipcode for an address based on city and state | | **Balance inquiry** `data247_balance_inquiry` | Check Data247 account balance and remaining credits | | **Carrier type** `data247_carrier_type` | Determine carrier type for USA and Canadian phone numbers | | **Dnc check** `data247_dnc_check` | Check if a phone number exists in Federal or internal Do-Not-Call list | | **Locate ip address** `data247_locate_ip_address` | Get geolocation data for IPv4 addresses including city, state, country, and coordinates | | **Lookup carrier usa** `data247_lookup_carrier_usa` | Look up carrier information for USA and Canadian phone numbers including carrier name, SMS/MMS | | **Lookup international carrier** `data247_lookup_international_carrier` | Get carrier information for international phone numbers worldwide | | **Text at** `data247_text_at` | Get carrier information, wireless status, and email-to-SMS/MMS gateway addresses for USA and | | **Trust phone** `data247_trust_phone` | Check if a phone number is on SPAM callers list | | **Trust user identity** `data247_trust_user_identity` | Verify user signup legitimacy and detect account creation fraud | | **Verify email** `data247_verify_email` | Verify email address format and mailbox existence | | **Verify phone** `data247_verify_phone` | Verify if a phone number is in-service and accepts inbound calls | | **Verify postal address** `data247_verify_postal_address` | Verify and correct USA postal addresses to USPS standards | | **Dnc add** `data247_dnc_add` | Add phone numbers to your internal do-not-call (DNC) list | | **Dnc remove** `data247_dnc_remove` | Remove phone numbers from your internal do-not-call (DNC) list | ## Example prompts **Append Email2** > Use Data247 to append email2 and walk me through the result in plain English. **Append Gender** > Use Data247 to append gender and walk me through the result in plain English. **Append Name** > Use Data247 to append name and walk me through the result in plain English. **Append Phone** > Use Data247 to append phone and walk me through the result in plain English. ## 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 Data247 working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Data247 API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Data247 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 Data247. | 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 Data247 actions to the runtime in a format your agent can reliably use. | 24 tools for Data247 are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Data247 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 Data247 in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Data247 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 Data247 skill but can't call the tools The ClawHub skill teaches OpenClaw about Data247, but the calls run through the ClawLink plugin and your connected account. Make sure Data247 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 Data247 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 Data247 tools Data247 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 Data247 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. ### Data247 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 Data247 has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Data247 integration? Yes. ClawLink is the fastest way to connect OpenClaw to Data247: link your Data247 account once in the browser and OpenClaw can call the Data247 API through 24 ready-made tools — no custom code or token handling. ### How do I add Data247 to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Data247 skill from ClawHub, then you click Connect in the dashboard to authorize Data247. OpenClaw calls the tools from the next message — no config files, and the Data247 key you paste is stored server-side instead of in your environment. ### How long does it take to connect Data247 to OpenClaw? About two minutes. Sign in, click Connect next to Data247 in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Data247 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 Data247 working from chat. ### OpenClaw installed the Data247 skill but can't call the tools The ClawHub skill teaches OpenClaw about Data247, but the calls run through the ClawLink plugin and your connected account. Make sure Data247 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.