# How to connect Push by Techulus to OpenClaw (paste one key, 6 tools) > Connect Push by Techulus to OpenClaw with ClawLink: paste your Push by Techulus key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/push-by-techulus The usual route to Push by Techulus 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 Push by Techulus setup: install one ClawHub skill, connect Push by Techulus in the browser, and OpenClaw can call real Push by Techulus 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 Push by Techulus. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Push by Techulus** — 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 push-by-techulus # connect Push by Techulus (browser OAuth) npx -y @useclawlink/cli actions push-by-techulus # list available actions npx -y @useclawlink/cli run push-by-techulus --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 Push by Techulus in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Push by Techulus API key once. Verify the connection by asking OpenClaw: > Use Push by Techulus to invite user to team 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 Push by Techulus is connected in the dashboard, that agent calls the same 6 Push by Techulus 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). ## Push by Techulus MCP for OpenClaw Looking for a Push by Techulus MCP server for OpenClaw? ClawLink connects Push by Techulus to OpenClaw and exposes 6 Push by Techulus 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 Push by Techulus integration](https://claw-link.dev/hermes/push-by-techulus) works the same way. ## What the OpenClaw Push by Techulus integration can do 6 Push by Techulus tools are ready for OpenClaw once the account is connected. The 5 below are the ones people reach for most; your agent can call all 6. ### 5 of 6 Push by Techulus tools for OpenClaw | Tool | What it does | |---|---| | **Invite user to team** `push_by_techulus_invite_user_to_team` | Invite a user to a team by sending an email invitation | | **Send notification async** `push_by_techulus_send_notification_async` | Send push notification asynchronously to all devices in an account or team | | **Send notification sync** `push_by_techulus_send_notification_sync` | Send push notifications synchronously to all linked devices | | **Send notification to group** `push_by_techulus_send_notification_to_group` | Send push notification to a specific device group | | **Send notification webhook post** `push_by_techulus_send_notification_webhook_post` | Send push notifications to all devices associated with a specific API key via POST request | ## Example prompts **Invite User To Team** > Use Push by Techulus to invite user to team and walk me through the result in plain English. **Send Notification Async** > Use Push by Techulus to send notification async for me and draft the message before sending. **Send Notification Sync** > Use Push by Techulus to send notification sync for me and draft the message before sending. **Send Notification To Group** > Use Push by Techulus to send notification to group for me and draft the message before sending. ## 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 Push by Techulus working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Push by Techulus API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Push by Techulus 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 Push by Techulus. | 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 Push by Techulus actions to the runtime in a format your agent can reliably use. | 6 tools for Push by Techulus are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Push by Techulus 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 Push by Techulus in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Push by Techulus 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 Push by Techulus skill but can't call the tools The ClawHub skill teaches OpenClaw about Push by Techulus, but the calls run through the ClawLink plugin and your connected account. Make sure Push by Techulus 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 Push by Techulus 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 Push by Techulus tools Push by Techulus 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 Push by Techulus 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. ### Push by Techulus 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 Push by Techulus has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Push by Techulus integration? Yes. ClawLink is the fastest way to connect OpenClaw to Push by Techulus: link your Push by Techulus account once in the browser and OpenClaw can call the Push by Techulus API through 6 ready-made tools — no custom code or token handling. ### How do I add Push by Techulus to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Push by Techulus skill from ClawHub, then you click Connect in the dashboard to authorize Push by Techulus. OpenClaw calls the tools from the next message — no config files, and the Push by Techulus key you paste is stored server-side instead of in your environment. ### How long does it take to connect Push by Techulus to OpenClaw? About two minutes. Sign in, click Connect next to Push by Techulus in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Push by Techulus 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 Push by Techulus working from chat. ### OpenClaw installed the Push by Techulus skill but can't call the tools The ClawHub skill teaches OpenClaw about Push by Techulus, but the calls run through the ClawLink plugin and your connected account. Make sure Push by Techulus 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 tools](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 - [SafetyCulture tools](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.