Apiflash Automation
It allows users to programmatically interact with Apiflash, streamlining tasks for those who need to manage website screenshots and related functionalities.
Install
npx promptshop add apiflash-automationDetails
What This Skill Does
This skill automates Apiflash operations using the Composio Apiflash toolkit through Rube MCP. It allows users to programmatically interact with Apiflash, streamlining tasks for those who need to manage website screenshots and related functionalities. It's designed for developers and automation engineers.
When to Use
- Automate website screenshot capture.
- Programmatically check website rendering.
- Integrate Apiflash into automated workflows.
- Monitor website changes visually.
- Create visual regression tests.
- Generate thumbnails of web pages.
Key Features
- Uses Rube MCP for tool access.
- Requires active Apiflash connection.
- Discovers available tools dynamically.
- Provides a structured workflow pattern.
- Emphasizes schema compliance.
- Offers connection status checks.
Manual Installation
Automate Apiflash operations through Composio's Apiflash toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/apiflash
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Apiflash connection via RUBE_MANAGE_CONNECTIONS with toolkit apiflash 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 apiflash 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: "Apiflash 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 Apiflash task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["apiflash"] 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 Apiflash-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit apiflash |
| 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 |
Automate Apiflash operations through Composio's Apiflash toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/apiflash