onesignal_rest_api-automationlisted

# 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": "push notifications, segments, templates, and messaging", "known_fields": ""}] ``` This returns: - Available tool slugs for OneSignal - Recommended execution plan steps - Known pitfalls and edge cases - Input schemas for each tool ## Core Workflows ### 1. Discover Available OneSignal Tools ``` RUBE_SEARCH_TOOLS: queries: - use_case: "list all available OneSignal tools and capabilities" ``` Review the returned tools, their descriptions