Integration

OneSignal integration

Push notification, email, SMS, and in-app messaging platform

Connect OneSignal How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in OneSignal.Built from the 21 OneSignal tools below, on the connection you add once.

Common OneSignal use cases

user removal
onboarding new users
retrieving user subscriptions
GDPR data deletion
user profile lookup
registering subscriptions

What you can do with OneSignal

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Device, 5 operations

add_deviceAdd devicePOSTRegister a new device
delete_deviceDelete deviceDELETEDelete a device
edit_deviceEdit devicePUTUpdate device properties
view_deviceView deviceGETGet device details
view_devicesView devicesGETList all devices

Notification, 4 operations

cancel_notificationCancel notificationDELETECancel scheduled notification
list_notificationsList notificationsGETList all notifications
send_notificationSend notificationPOSTSend push notification
view_notificationView notificationGETGet notification details

Segment, 3 operations

create_segmentCreate segmentPOSTCreate user segment
delete_segmentDelete segmentDELETEDelete a segment
list_segmentsList segmentsGETList all segments

User, 3 operations

create_userCreate userPOSTCreate or update a user with the modern Users API.
delete_userDelete userDELETEDelete a user by alias using the modern Users API.
get_userGet userGETRetrieve a user by alias using the modern Users API.

App, 2 operations

list_appsList appsGETList all apps
view_appView appGETGet app settings

Template, 2 operations

create_templateCreate templatePOSTCreate notification template
list_templatesList templatesGETList notification templates

Outcome, 1 operation

get_outcomesGet outcomesGETGet notification outcomes

Player, 1 operation

export_playersExport playersPOSTExport players to CSV

Use OneSignal from Claude Code, Cursor or Codex

Connect OneSignal in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its OneSignal operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect OneSignal

Create your workspace
Sign up free. Nothing to install.
Connect OneSignal once
Add your OneSignal connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

OneSignal integration FAQ

What can you do with the OneSignal integration?

LiveContext exposes 21 operations on OneSignal, covering device, notification, segment and user. Common uses include user removal, onboarding new users and retrieving user subscriptions.