onesignal-rest-api-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/onesignal-rest-api-automation --openclawOneSignal Automation via Rube MCP
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_CONNECTIONSwith toolkitonesignal_rest_api - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitonesignal_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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with OneSignal-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit onesignal_rest_api |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/onesignal-rest-api-automation/SKILL.mdView on GitHub Overview
Automate OneSignal operations by leveraging Composio's onesignal_rest_api toolkit through Rube MCP. The process emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and executing tools via RUBE_MULTI_EXECUTE_TOOL. This approach keeps integrations up to date and reduces manual setup.
How This Skill Works
First, discover available tools using RUBE_SEARCH_TOOLS to get up-to-date slugs and input schemas. Then verify the OneSignal connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally run tools with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, correct arguments, and memory payload; include session_id and memory even if empty.
When to Use It
- Automating OneSignal tasks (e.g., campaigns, segments, templates) using Composio's OneSignal toolkit
- Integrating OneSignal operations into larger workflows that require current tool schemas (no hardcoding)
- Setting up a new Rube MCP connection to OneSignal and validating ACTIVE status before workflows
- Staging OneSignal data updates or queries with session management across multiple steps
- Performing bulk or multi-tool tasks using RUBE_MULTI_EXECUTE_TOOL within a session
Quick Start
- Step 1: Run RUBE_SEARCH_TOOLS with use_case: "OneSignal operations" to discover available tools
- Step 2: Run RUBE_MANAGE_CONNECTIONS for toolkit onesignal_rest_api and ensure the status is ACTIVE
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {}, and the session_id
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch latest tool slugs and schemas
- Confirm RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
- Use exact field names and types from the discovered schemas; avoid hardcoding
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and refresh for new tasks as needed
Example Use Cases
- Automate creating a OneSignal campaign by discovering the campaign tool slug and required fields, then executing with current schema
- Update a device segment by fetching the correct segment tool via RUBE_SEARCH_TOOLS and running with the appropriate arguments
- Fetch and list OneSignal templates through a discovered tool and output the results
- Perform bulk device updates using RUBE_REMOTE_WORKBENCH and run_composio_tool on multiple tools in sequence
- Handle paginated results when listing campaigns or audiences by continuing with pagination tokens until complete
