Use OneSignal REST API from Claude
Add the OneSignal REST API connection to a Space that runs Claude, then use it from every channel in that Space.
Connect OneSignal REST API once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the OneSignal REST API connection to a Space that runs Claude, then use it from every channel in that Space.
Add the OneSignal REST API connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
OneSignal handles push, email, SMS, and in-app messaging for an app's user base, with templates and user profiles kept in one account. Once a team connects OneSignal REST API in type.com, the agent can draft a notification, start a Live Activity, or create a reusable template, and teammates review the exact message before it reaches users.
Connect OneSignal REST API once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Describe the audience and message and have the agent create the notification instead of switching to the OneSignal dashboard.
Create a OneSignal push notification announcing the new feature to users tagged as active this week.
Turn a recurring announcement into a template so future notifications pull the same format automatically.
Create a OneSignal template for our weekly digest push notification.
Start a Live Activity when an event needs a running status on a user's lock screen or app.
Begin a OneSignal Live Activity for order 4821 using the delivery tracking token.
Starts a Live Activity session on a device using a push token and subscription ID.
Builds and sends a push notification once the message and target audience are set.
Saves a reusable message template for push, email, or SMS that the dashboard and API can both use.
Adds a OneSignal user record, optionally with subscriptions and alias identifiers attached.
Removes a named alias from a user's profile without deleting the user record itself.
OneSignal REST API supports customer messaging across push, email, SMS, in-app, and Live Activities. Integrations can send notifications, manage apps, users, subscriptions, segments, templates, outcomes, aliases, and Journeys-adjacent messaging data using REST API keys.
Yes. Once a OneSignal connection is shared with a type.com Space, the agent can draft and send a notification, build a template, or start a Live Activity from any thread, with results visible to the team.
OneSignal uses an API key. An admin adds it once to the connection and picks which Spaces can use it, so the key never appears in a prompt.
Yes. Turn a OneSignal prompt into a type.com automation, such as a recurring weekly digest notification, and the agent sends it and posts a confirmation to the channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Sendbird to Claude in type.com to create channels, add members, and moderate users from a shared thread.
Connect SMS Alert to Claude in type.com to check balance, pull delivery reports, and manage groups from a thread.
Connect Smtp2go to Claude in type.com to search email activity, manage allowed senders, and investigate delivery issues from a shared thread.
Connect Telnyx to Claude in type.com to provision networks, set up notification channels and profiles, and manage alerts from a shared team thread.