Skip to main content

composio-onesignal-rest-api-automation

Automate OneSignal tasks via Rube MCP (Composio). Always search tools first for current schemas.

Informations de source

Dépôt
GrayCodeAI/hawk-community-skills
Dernière activité de la source
27 mai 2026 à 18:10
Langue détectée de SKILL.md
anglais
Étoiles
1
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
composio-onesignal-rest-api-automation
description
Automate OneSignal tasks via Rube MCP (Composio). Always search tools first for current schemas.
license
MIT
tags
["general"]
requires
None
mcp
["rube"]
# OneSignal Automation via Rube MCP Automate OneSignal operations through Composio's OneSignal toolkit via Rube MCP. **Toolkit docs**: [composio.dev/toolkits/onesignal_rest_api](https://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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. 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 | 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](https://composio.dev)*
Voir sur GitHub