# How to connect OneSignal REST API to Hermes Agent (paste one key, 15 tools)

> Connect OneSignal REST API to Hermes with ClawLink: paste your OneSignal REST API key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/onesignal-rest-api

Most guides for giving Hermes Agent OneSignal REST API access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical OneSignal REST API setup: pair once in the browser and your always-on Hermes agent can act on OneSignal REST API for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to OneSignal REST API.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect OneSignal REST API** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 onesignal-rest-api  # connect OneSignal REST API (browser OAuth)
npx -y @useclawlink/cli actions onesignal-rest-api  # list available actions
npx -y @useclawlink/cli run onesignal-rest-api <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect OneSignal REST API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your OneSignal REST API API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from OneSignal REST API, summarize it in plain English, and point out anything that needs attention.

### Using a different agent?

The Hermes 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 OneSignal REST API is connected in the dashboard, that agent calls the same 15 OneSignal REST API 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).

## OneSignal REST API MCP for Hermes

Looking for a OneSignal REST API MCP server for Hermes Agent? ClawLink connects OneSignal REST API to Hermes Agent and exposes 15 OneSignal REST API 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 OpenClaw instead? The [OpenClaw OneSignal REST API integration](https://claw-link.dev/openclaw/onesignal-rest-api) works the same way.

## What the Hermes Agent OneSignal REST API integration can do

15 OneSignal REST API tools are ready for Hermes Agent once the account is connected. The 13 below are the ones people reach for most; your agent can call all 15.

### 13 of 15 OneSignal REST API tools for Hermes

| Tool | What it does |
|---|---|
| **Fetch user identity** `onesignal_rest_api_fetch_user_identity` | Retrieve all aliases for a user identified by a specific alias |
| **Get eligible iams** `onesignal_rest_api_get_eligible_iams` | Retrieve the manifest of In-App Messages that a subscription is eligible to display |
| **View an app** `onesignal_rest_api_view_an_app` | Retrieve metadata for a single OneSignal app |
| **View device** `onesignal_rest_api_view_device` | Retrieve details of a specific device (player) |
| **View devices** `onesignal_rest_api_view_devices` | Retrieve a paginated list of devices (players) for a OneSignal app |
| **View notifications** `onesignal_rest_api_view_notifications` | Retrieve details of multiple notifications |
| **View segments** `onesignal_rest_api_view_segments` | View segments for a OneSignal app |
| **Begin live activity** `onesignal_rest_api_begin_live_activity` | Start a Live Activity on OneSignal |
| **Create notification** `onesignal_rest_api_create_notification` | Create and send a OneSignal push notification |
| **Create template** `onesignal_rest_api_create_template` | Create reusable message templates for push, email, and SMS channels |
| **Create user** `onesignal_rest_api_create_user` | Create a OneSignal user with optional subscriptions and aliases |
| **Update device** `onesignal_rest_api_update_device` | Update properties of an existing device |
| **Update subscription** `onesignal_rest_api_update_subscription` | Update an existing subscription's properties |

## Example prompts

**Fetch User Identity**

> Pull the relevant data from OneSignal REST API, summarize it in plain English, and point out anything that needs attention.

**Get Eligible Iams**

> Pull the relevant data from OneSignal REST API, summarize it in plain English, and point out anything that needs attention.

**View An App**

> Use OneSignal REST API to view an app and walk me through the result in plain English.

**View Device**

> Use OneSignal REST API to view device 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want OneSignal REST API working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the OneSignal REST API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OneSignal REST API 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 OneSignal REST API. | 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 OneSignal REST API actions to the runtime in a format your agent can reliably use. | 15 tools for OneSignal REST API are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes OneSignal REST API 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 Hermes Agent users instead. You install the plugin once, connect OneSignal REST API in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the OneSignal REST API 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.

### Hermes paired but still can't use OneSignal REST API
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### Connection succeeds but no tools appear
Reconnect OneSignal REST API 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 OneSignal REST API tools
OneSignal REST API 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 OneSignal REST API 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.

### OneSignal REST API 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 OneSignal REST API has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a Hermes Agent OneSignal REST API integration?
Yes. ClawLink is the fastest way to connect Hermes to OneSignal REST API: link your OneSignal REST API account once in the browser and Hermes Agent can call the OneSignal REST API API through 15 ready-made tools — no custom code or token handling.

### How do I connect OneSignal REST API to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect OneSignal REST API in the dashboard and Hermes can use it from the next message — no config files, and the OneSignal REST API key you paste is stored server-side instead of in your environment.

### How long does it take to connect OneSignal REST API to Hermes Agent?
About two minutes. Sign in, click Connect next to OneSignal REST API in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring OneSignal REST API up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want OneSignal REST API working from chat.

### Hermes paired but still can't use OneSignal REST API
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [SendGrid](https://claw-link.dev/hermes/sendgrid) — Deliver transactional and marketing emails
- [Connect Dialpad](https://claw-link.dev/hermes/dialpad) — Business phone, messaging, and video conferencing
- [Discord Bot tools](https://claw-link.dev/hermes/discord-bot) — Automate Discord server actions with bot-specific permissions