Onesignal Rest API Automation

What This Skill Does

This skill automates OneSignal operations using Composio's OneSignal toolkit via Rube MCP. It allows users to manage push notifications, segments, and messaging through a structured workflow. This is useful for developers and marketers looking to streamline their OneSignal interactions.

When to Use

• Send targeted push notifications.
• Manage user segments in OneSignal.
• Automate message template creation.
• Update existing OneSignal configurations.
• Trigger notifications based on user behavior.
• Schedule push notifications for optimal delivery.

Key Features

• Automates OneSignal tasks via Rube MCP.
• Uses Composio's OneSignal toolkit.
• Requires an active OneSignal connection.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for OneSignal operations.

Manual Installation

Automate OneSignal operations through Composio's OneSignal toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/onesignal_rest_api

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active OneSignal connection via RUBE_MANAGE_CONNECTIONS with toolkit onesignal_rest_api Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit onesignal_rest_api If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "OneSignal operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific OneSignal task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["onesignal_rest_api"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Automate OneSignal operations through Composio's OneSignal toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/onesignal_rest_api

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active OneSignal connection via RUBE_MANAGE_CONNECTIONS with toolkit onesignal_rest_api Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit onesignal_rest_api If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "OneSignal operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific OneSignal task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["onesignal_rest_api"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference