diff --git a/sources/platform/integrations/ai/index.mdx b/sources/platform/integrations/ai/index.mdx index ee4696263c..0b3b4211c4 100644 --- a/sources/platform/integrations/ai/index.mdx +++ b/sources/platform/integrations/ai/index.mdx @@ -96,6 +96,13 @@ Plug Apify Actors into the AI stack - chat clients like Claude and ChatGPT via t imageUrlDarkTheme="/img/platform/integrations/cursor-white.svg" smallImage /> + ## By provider @@ -104,4 +111,6 @@ The [Claude hub](/integrations/claude) covers Apify integrations across Claude D The [OpenAI hub](/integrations/openai) covers Apify integrations across ChatGPT, the OpenAI Agents SDK, and OpenAI Assistants on one page. +The [Qoder hub](/integrations/qoder) covers the Apify plugin across the Qoder CLI, the Qoder IDE, and QoderWork on one page. + For Google ADK, see the [Google ADK](/integrations/google-adk) page. The full list of AI integrations lives in the sidebar. diff --git a/sources/platform/integrations/ai/qoder/_category_.yml b/sources/platform/integrations/ai/qoder/_category_.yml new file mode 100644 index 0000000000..eaafc950c5 --- /dev/null +++ b/sources/platform/integrations/ai/qoder/_category_.yml @@ -0,0 +1 @@ +label: 'Qoder' diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/01-plugins.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/01-plugins.webp new file mode 100644 index 0000000000..abe6d2c835 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/01-plugins.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/02-add-marketplace.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/02-add-marketplace.webp new file mode 100644 index 0000000000..38b247a5ee Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/02-add-marketplace.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/03-link-marketplace.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/03-link-marketplace.webp new file mode 100644 index 0000000000..e5fc0ce37c Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/03-link-marketplace.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/04-discover.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/04-discover.webp new file mode 100644 index 0000000000..4ba57fc77e Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/04-discover.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/05-install-plugin.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/05-install-plugin.webp new file mode 100644 index 0000000000..4b4abb21cc Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/05-install-plugin.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/06-check-installed.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/06-check-installed.webp new file mode 100644 index 0000000000..28d25de1e1 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/06-check-installed.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/07-find-mcp.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/07-find-mcp.webp new file mode 100644 index 0000000000..c6589c9d68 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/07-find-mcp.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/08-mcp-authenticate.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/08-mcp-authenticate.webp new file mode 100644 index 0000000000..921ddcac5e Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/08-mcp-authenticate.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/09-consent.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/09-consent.webp new file mode 100644 index 0000000000..e4bba4f1f3 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/09-consent.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/10-authenticating.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/10-authenticating.webp new file mode 100644 index 0000000000..f01b788ec4 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/10-authenticating.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/11-browser-success.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/11-browser-success.webp new file mode 100644 index 0000000000..639cd614d1 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/11-browser-success.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/12-mcp-ready.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/12-mcp-ready.webp new file mode 100644 index 0000000000..f3f09f3900 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/12-mcp-ready.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/13-view-tools.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/13-view-tools.webp new file mode 100644 index 0000000000..8ab62e6091 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/13-view-tools.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/14-test.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/14-test.webp new file mode 100644 index 0000000000..c075e0e91c Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-cli/14-test.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/1-settings.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/1-settings.webp new file mode 100644 index 0000000000..b8abed860a Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-ide/1-settings.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/2-import.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/2-import.webp new file mode 100644 index 0000000000..b79f4d3fd5 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-ide/2-import.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/3-plugin-listed.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/3-plugin-listed.webp new file mode 100644 index 0000000000..8616ef4de7 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-ide/3-plugin-listed.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/4-mcp-login.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/4-mcp-login.webp new file mode 100644 index 0000000000..43b5486e59 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-ide/4-mcp-login.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/5-test-plugin.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/5-test-plugin.webp new file mode 100644 index 0000000000..8a487d9c99 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-ide/5-test-plugin.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/1-upload-plugin.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/1-upload-plugin.webp new file mode 100644 index 0000000000..0cc2f27269 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-work/1-upload-plugin.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/2-activate-login.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/2-activate-login.webp new file mode 100644 index 0000000000..7ceeee96ab Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-work/2-activate-login.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/3-tools-list.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/3-tools-list.webp new file mode 100644 index 0000000000..bbabfb8de7 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-work/3-tools-list.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/4-activate-plugin.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/4-activate-plugin.webp new file mode 100644 index 0000000000..081fb3d4b7 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-work/4-activate-plugin.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/5-chat-list-tools.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/5-chat-list-tools.webp new file mode 100644 index 0000000000..ba30e3c499 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qoder-work/5-chat-list-tools.webp differ diff --git a/sources/platform/integrations/ai/qoder/index.mdx b/sources/platform/integrations/ai/qoder/index.mdx new file mode 100644 index 0000000000..42bb60013d --- /dev/null +++ b/sources/platform/integrations/ai/qoder/index.mdx @@ -0,0 +1,37 @@ +--- +title: Qoder +description: Use Apify Actors with Qoder - install the Apify plugin in the Qoder CLI, the Qoder IDE, or QoderWork to discover, run, and build Actors as tools. +sidebar_label: Qoder +slug: /integrations/qoder +--- + +import Card from '@site/src/components/Card'; +import CardGrid from '@site/src/components/CardGrid'; + +Apify integrates with [Qoder](https://qoder.com), an agentic coding platform, through the Apify plugin. The same plugin installs in the Qoder CLI, the Qoder IDE, and QoderWork, and gives Qoder a way to call Apify Actors as tools and read their results. + +## What you can build + + + + + + diff --git a/sources/platform/integrations/ai/qoder/qoder-cli.md b/sources/platform/integrations/ai/qoder/qoder-cli.md new file mode 100644 index 0000000000..8a223495b0 --- /dev/null +++ b/sources/platform/integrations/ai/qoder/qoder-cli.md @@ -0,0 +1,179 @@ +--- +title: Qoder CLI integration +sidebar_label: Qoder CLI +description: Learn how to install the Apify plugin for the Qoder CLI to discover, run, and build Actors with the Apify MCP server, skills, and a routing agent. +slug: /integrations/qoder-cli +--- + +import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; + +[Qoder CLI](https://qoder.com) is an agentic coding tool that runs in your terminal. It reads and edits your codebase, runs commands, and completes multi-step development tasks. + +The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) connects the Qoder CLI to Apify's library of [Actors](https://apify.com/store) and bundles: + +- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). +- An `apify` routing agent that picks the right tool or skill from a natural-language request. +- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). + + + +## Prerequisites + +- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. +- [Qoder CLI](https://qoder.com) - installed and signed in locally. + +## Install the plugin + +1. In the Qoder CLI, run `/plugins` to open the plugin manager. + + ![Qoder CLI with the /plugins command entered](images/qoder-cli/01-plugins.webp) + +1. Open the **Marketplaces** tab and select **+ Add marketplace**. + + ![Qoder CLI plugin manager on the Marketplaces tab with Add marketplace selected](images/qoder-cli/02-add-marketplace.webp) + +1. Paste the Apify plugin repository URL and press Enter: + + ```text + https://github.com/apify/apify-qoder-plugin + ``` + + ![Add Marketplace prompt with the Apify plugin repository URL entered](images/qoder-cli/03-link-marketplace.webp) + +1. Open the **Discover** tab. The `apify` plugin appears in the list. Press Enter to view its details. + + ![Discover tab listing the apify plugin](images/qoder-cli/04-discover.webp) + +1. Review the plugin details and trust warning, then select **Install (user scope)** and press Enter. + + ![apify plugin detail with the install scope options and a trust warning](images/qoder-cli/05-install-plugin.webp) + +1. Run `/plugins reload` to apply the changes, then restart the Qoder CLI so the bundled MCP server registers (see the tip below). + +1. Open the **Installed** tab to confirm the `apify` plugin is enabled and its MCP server shows as connected. + + ![Installed tab showing the apify plugin enabled and apify MCP connected](images/qoder-cli/06-check-installed.webp) + +:::tip Restart the CLI so the MCP server registers + +The Apify MCP server registers when the Qoder CLI starts, not on `/plugins reload`. If `/mcp` shows no Apify server after installing, fully quit and reopen the Qoder CLI. + +::: + +## Authenticate to Apify + +The plugin bundles the Apify MCP server. Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. + +1. Run `/mcp` to open the MCP server manager and select **Plugin** to list plugin-provided servers. + + ![MCP server manager listing plugin:apify:apify under the Plugin tab](images/qoder-cli/07-find-mcp.webp) + +1. Select **plugin:apify:apify** to open its details. The status reads **needs authentication**. Select **Authenticate**. + + ![plugin:apify:apify server detail with a needs authentication status and the Authenticate option](images/qoder-cli/08-mcp-authenticate.webp) + +1. At the consent prompt, select **Yes** to open the Apify authentication page in your browser. + + ![Consent prompt asking whether to continue with authentication](images/qoder-cli/09-consent.webp) + +1. The Qoder CLI waits for the browser callback. If the browser doesn't open automatically, copy the full URL shown in the terminal and paste it into your browser. + + ![Terminal waiting for the browser callback and showing the fallback OAuth URL](images/qoder-cli/10-authenticating.webp) + +1. In the browser, review the permissions and allow access. A confirmation page tells you to close the window and return to the Qoder CLI. + + ![Browser page confirming authentication was successful](images/qoder-cli/11-browser-success.webp) + +1. Back in the terminal, the server status changes to **ready** and the Apify tools become available. + + ![plugin:apify:apify server detail showing a ready status with 11 tools](images/qoder-cli/12-mcp-ready.webp) + +To see what the agent can call, select **View tools** on the server detail. The Apify MCP server exposes 11 tools, each labeled read-only, destructive, or open-world. + +![Tools view listing the 11 Apify MCP tools with their annotations](images/qoder-cli/13-view-tools.webp) + +:::tip Session persistence + +The connection stays authenticated for future sessions. You can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). + +::: + +## Run your first prompt + +Describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. + +> List what Apify tools you have available. + +The agent lists the Apify MCP tools and skills it can call, grouped by purpose. + +![Qoder CLI listing the available Apify MCP tools and skills](images/qoder-cli/14-test.webp) + +To go further, ask it to find an Actor for a task: + +> Use Apify to find a good Actor for scraping Google Maps places. Show me the best option, its input requirements, pricing model, and what kind of dataset output it returns. Do not run the Actor yet. + +## Bundled skills + +| Skill | Description | +| --- | --- | +| `apify-ultimate-scraper` | CLI-driven extraction using existing Actors for multi-step scraping and lead-generation workflows. | +| `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | +| `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | +| `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | + +Example prompts that route to specific skills: + +_Ultimate scraper:_ + +> Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. + +_Actor development:_ + +> Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. + +_SDK integration:_ + +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. + +## Troubleshooting + +### The Apify MCP server doesn't appear + +Run `/mcp` and check the **Plugin** list. If no Apify server is shown, the plugin was installed but the server hasn't registered yet. The server registers at startup, so fully quit and reopen the Qoder CLI, then check again. + +### The `apify` plugin is disabled + +Run `/plugins`, open the **Installed** tab, select the `apify` plugin, and enable it. Run `/plugins reload` to apply the change in the current session. + +### The `/plugins` command isn't available + +Plugins require a local installation of the Qoder CLI. Install or update the Qoder CLI locally, then run `/plugins` again. + +### Browser doesn't open, or OAuth fails + +If the browser doesn't open automatically, copy the OAuth URL shown in the terminal and paste it into your browser manually. + +If you're running the Qoder CLI in a headless environment (SSH, remote container) or the OAuth flow still fails, authenticate with an API token instead. Copy your token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations) and set it before starting the Qoder CLI: + +```bash +export APIFY_TOKEN= +``` + +## Limitations + +- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. +- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. + +## Related integrations + +- [Qoder IDE integration](/integrations/qoder-ide) - Import the same plugin in the Qoder IDE +- [QoderWork integration](/integrations/qoder-work) - Upload the plugin in QoderWork +- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients + +## Resources + +- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes +- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs +- [Apify Store](https://apify.com/store) - Browse Actors you can run from the Qoder CLI diff --git a/sources/platform/integrations/ai/qoder/qoder-ide.md b/sources/platform/integrations/ai/qoder/qoder-ide.md new file mode 100644 index 0000000000..10ecbcaf92 --- /dev/null +++ b/sources/platform/integrations/ai/qoder/qoder-ide.md @@ -0,0 +1,100 @@ +--- +title: Qoder IDE integration +sidebar_label: Qoder IDE +description: Learn how to import the Apify plugin in the Qoder IDE to discover, run, and build Actors with the Apify MCP server, skills, and a routing agent. +slug: /integrations/qoder-ide +--- + +import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; + +[Qoder IDE](https://qoder.com) is an agentic coding editor. It reads and edits your project, runs commands, and completes multi-step development tasks from a built-in chat. + +The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) connects the Qoder IDE to Apify's library of [Actors](https://apify.com/store) and bundles: + +- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). +- An `apify` routing agent that picks the right tool or skill from a natural-language request. +- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). + + + +## Prerequisites + +- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. +- [Qoder IDE](https://qoder.com) - installed and signed in. +- A local copy of the [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - clone or download the repository so you can import it. + +## Import the plugin + +1. Open the account menu and select **Qoder Settings**. + + ![Qoder IDE account menu with Qoder Settings selected](images/qoder-ide/1-settings.webp) + +1. Select **Plugins**, then under **Custom** select **Import**. + + ![Qoder Settings Plugins page with the Custom section and Import action](images/qoder-ide/2-import.webp) + +1. Select the Apify plugin folder from your local copy of the repository. The **Apify Qoder Plugin** appears under **Custom**, enabled for your user. + + ![Plugins page showing the imported Apify Qoder Plugin enabled under Custom](images/qoder-ide/3-plugin-listed.webp) + +1. Select **MCP Server** to confirm the `apify` server is registered from the plugin. It connects to `https://mcp.apify.com` and exposes the Apify tools. + + ![MCP Server page listing the apify server from the plugin with its tools](images/qoder-ide/4-mcp-login.webp) + +## Authenticate to Apify + +Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. + +On the first action that needs your account, the Qoder IDE opens a browser tab for the Apify OAuth flow. Review the permissions and allow access to finish signing in. The connection stays authenticated for future sessions, and you can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). + +## Run your first prompt + +Open the chat and describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. + +> What Apify tools do you have available? + +The agent lists the Apify MCP tools and skills it can call. + +![Qoder IDE chat listing the available Apify tools and skills](images/qoder-ide/5-test-plugin.webp) + +## Bundled skills + +| Skill | Description | +| --- | --- | +| `apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | +| `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | +| `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | +| `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | + +## Troubleshooting + +### The Apify server doesn't appear under MCP Server + +Confirm the **Apify Qoder Plugin** is enabled on the **Plugins** page, then open the **MCP Server** page again. If the server is still missing, restart the Qoder IDE so the plugin's MCP server registers. + +### Actor runs time out + +Increase the request timeout for the `apify` server on the **MCP Server** page. Long-running Actors may still exceed the limit; reduce the scope or split the work across multiple prompts. + +### Browser doesn't open, or OAuth fails + +If the browser doesn't open automatically, copy the OAuth URL shown by the IDE and paste it into your browser manually. If sign-in still fails, authenticate with an API token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). + +## Limitations + +- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. +- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. + +## Related integrations + +- [Qoder CLI integration](/integrations/qoder-cli) - Install the same plugin in the Qoder CLI +- [QoderWork integration](/integrations/qoder-work) - Upload the plugin in QoderWork +- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients + +## Resources + +- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes +- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs +- [Apify Store](https://apify.com/store) - Browse Actors you can run from the Qoder IDE diff --git a/sources/platform/integrations/ai/qoder/qoder-work.md b/sources/platform/integrations/ai/qoder/qoder-work.md new file mode 100644 index 0000000000..39024be65d --- /dev/null +++ b/sources/platform/integrations/ai/qoder/qoder-work.md @@ -0,0 +1,106 @@ +--- +title: QoderWork integration +sidebar_label: QoderWork +description: Learn how to upload the Apify plugin in QoderWork to discover, run, and build Actors with the Apify MCP server connector, skills, and a routing agent. +slug: /integrations/qoder-work +--- + +import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; + +[QoderWork](https://qoder.com) is a desktop assistant for knowledge work. It runs tasks and chats using role-oriented plugins that bundle MCP connectors, skills, and agents. + +The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) adds Apify to QoderWork and bundles: + +- The [Apify MCP server](/integrations/mcp) as a connector for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). +- An `apify` routing agent that picks the right tool or skill from a natural-language request. +- Five built-in skills, available as quick commands (see [Bundled skills](#bundled-skills) below). + + + +## Prerequisites + +- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. +- [QoderWork](https://qoder.com) - installed and signed in. +- A local copy of the [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - download the plugin bundle so you can upload it. + +## Upload the plugin + +1. Open **Plugins**, select **+ Add**, then select **Upload plugin**. + + ![QoderWork Plugins page with the Add menu open and Upload plugin selected](images/qoder-work/1-upload-plugin.webp) + +1. Select the Apify plugin bundle from your local copy. The `apify` plugin is installed for local use and appears under your custom plugins. + +## Authenticate the Apify connector + +The plugin adds Apify as a connector. Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. + +1. Open the `apify` plugin. Under **Connectors**, the Apify connector shows **Authentication required**. Select **Auth**. + + ![Apify connector showing Authentication required with the Auth action](images/qoder-work/2-activate-login.webp) + +1. Complete the Apify OAuth flow in your browser and allow access. The connector then reports its available tools. + + ![Apify connector connected and listing its tools](images/qoder-work/3-tools-list.webp) + +The connection stays authenticated for future sessions. You can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). + +## Enable the plugin in chat + +1. On the plugin page, turn on **Enable in chat**. The plugin's quick commands and connector become available in tasks and chat. + + ![Apify plugin page with quick commands, the Apify connector, and Enable in chat](images/qoder-work/4-activate-plugin.webp) + +1. Start a task or chat and describe what you want. The `apify` agent routes the request to the right tool or skill. + + > List available Apify tools. + + ![QoderWork chat listing the available Apify tools](images/qoder-work/5-chat-list-tools.webp) + +## Bundled skills + +Each skill is available as a quick command. Type `/` in a task or chat to run one directly. + +| Quick command | Description | +| --- | --- | +| `/apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | +| `/apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | +| `/apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | +| `/apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `/apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | + +## Widget tools + +In QoderWork, the Apify connector also exposes interactive widget variants of its core tools - `search-actors-widget`, `fetch-actor-details-widget`, `call-actor-widget`, and `get-actor-run-widget`. They render Actor search, details, runs, and run status as interactive UI elements in chat instead of plain text. + +## Troubleshooting + +### The Apify connector stays on "Authentication required" + +Open the `apify` plugin, select **Auth** on the Apify connector, and complete the browser sign-in. If the browser doesn't open automatically, copy the OAuth URL and paste it into your browser manually. + +### Tools don't appear in chat + +Confirm **Enable in chat** is turned on for the `apify` plugin and that the Apify connector is authenticated. Reopen the task or chat after enabling the plugin. + +### Actor runs time out + +Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. + +## Limitations + +- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. +- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. +- Skills that edit files (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. + +## Related integrations + +- [Qoder CLI integration](/integrations/qoder-cli) - Install the same plugin in the Qoder CLI +- [Qoder IDE integration](/integrations/qoder-ide) - Import the plugin in the Qoder IDE +- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients + +## Resources + +- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes +- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs +- [Apify Store](https://apify.com/store) - Browse Actors you can run from QoderWork diff --git a/sources/platform/integrations/index.mdx b/sources/platform/integrations/index.mdx index fa353b41f5..4901fffb4d 100644 --- a/sources/platform/integrations/index.mdx +++ b/sources/platform/integrations/index.mdx @@ -131,6 +131,13 @@ Plug Apify Actors into the AI stack - chat clients like Claude and ChatGPT via t imageUrlDarkTheme="/img/platform/integrations/cursor-white.svg" smallImage /> + [See all AI integrations →](/integrations/ai) diff --git a/static/img/platform/integrations/qoder-cli.png b/static/img/platform/integrations/qoder-cli.png new file mode 100644 index 0000000000..aa0a887044 Binary files /dev/null and b/static/img/platform/integrations/qoder-cli.png differ diff --git a/static/img/platform/integrations/qoder-work.png b/static/img/platform/integrations/qoder-work.png new file mode 100644 index 0000000000..5591b5e175 Binary files /dev/null and b/static/img/platform/integrations/qoder-work.png differ diff --git a/static/img/platform/integrations/qoder.png b/static/img/platform/integrations/qoder.png new file mode 100644 index 0000000000..5b784908bb Binary files /dev/null and b/static/img/platform/integrations/qoder.png differ