Skip to content

Conversation

@drobnikj
Copy link

@drobnikj drobnikj commented Dec 3, 2025

This pull request adds support for the Apify integration, enabling users to run Apify Actors and perform single-URL web scraping within workflows.

Apify Integration

  • Added Apify integration plugin (plugins/apify/index.tsx), including form fields for API token, test function, and two actions: "Run Actor" and "Scrape Single URL", each with configuration fields and codegen templates.
  • Registered Apify actions in the step registry (lib/step-registry.ts, lib/steps/index.ts), updated action labels, and integration types to include Apify.

New UI Components

  • Added TemplateBadgeJson component for real-time JSON validation and formatting in action configuration.
  • Updated workflow action config to use specialized fields for Apify "Run Actor" action.

yfe404 and others added 17 commits November 27, 2025 16:12
Adds a new "Run Actor" action that allows workflows to execute Apify Actors.

Features:
- Integration setup with API token configuration
- Actor selection by ID (e.g., apify/rag-web-browser)
- JSON input support for Actor parameters
- Sync/async execution modes
- Full input/output display in Runs panel
- Connection testing

Files added:
- plugins/apify/ - Complete plugin implementation

Files modified:
- action-grid.tsx, action-config.tsx - UI for Run Actor action
- workflow-executor.workflow.ts - Runtime execution handler
- credential-fetcher.ts - API key mapping
- integration-form-dialog.tsx - Settings form
- test/route.ts - Connection test endpoint

Limitations:
- Icon is a placeholder, not the official Apify logo
@vercel
Copy link
Contributor

vercel bot commented Dec 3, 2025

@drobnikj is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

bensabic

This comment was marked as resolved.

@drobnikj
Copy link
Author

drobnikj commented Dec 4, 2025

@bensabic thanks for review, is there anything I can do to merge this?

README.md Outdated
Comment on lines 276 to 277
scrapeSingleUrlStep,
apifyRunActorStep,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The README shows an incorrect import path that doesn't exist, which would cause a runtime import error when users follow the documentation.

View Details
📝 Patch Details
diff --git a/lib/steps/apify.ts b/lib/steps/apify.ts
new file mode 100644
index 0000000..2213ef0
--- /dev/null
+++ b/lib/steps/apify.ts
@@ -0,0 +1,6 @@
+/**
+ * Apify steps - barrel export for public API
+ */
+
+export { apifyRunActorStep } from "../../plugins/apify/steps/run-actor/step";
+export { scrapeSingleUrlStep } from "../../plugins/apify/steps/scrape-single-url/step";

Analysis

Missing barrel export for Apify step functions in README documentation

What fails: README.md (lines 276-278) shows an import statement from @/lib/steps/apify, but this barrel export file does not exist. TypeScript compilation fails with error TS2307: Cannot find module '@/lib/steps/apify'.

How to reproduce:

  1. Create a TypeScript file with the import from README:
import {
  scrapeSingleUrlStep,
  apifyRunActorStep,
} from "@/lib/steps/apify";
  1. Run pnpm type-check before the fix - fails with error TS2307: Cannot find module '@/lib/steps/apify'

What happened: Users following the README documentation would be unable to import these functions from the documented path. The functions exist in plugins/apify/steps/run-actor/step.ts and plugins/apify/steps/scrape-single-url/step.ts but are not re-exported from any barrel file that matches the import path shown in the documentation.

Expected: The README example should work without TypeScript errors. The fix creates a barrel export file at lib/steps/apify.ts that re-exports both functions, allowing the documented import path to work correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants