-
Notifications
You must be signed in to change notification settings - Fork 131
feat: Add Apify Scrape Single URL and Run Actor actions #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
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
|
@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 thanks for review, is there anything I can do to merge this? |
# Conflicts: # pnpm-lock.yaml
README.md
Outdated
| scrapeSingleUrlStep, | ||
| apifyRunActorStep, |
There was a problem hiding this comment.
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:
- Create a TypeScript file with the import from README:
import {
scrapeSingleUrlStep,
apifyRunActorStep,
} from "@/lib/steps/apify";- Run
pnpm type-checkbefore the fix - fails witherror 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.
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
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.lib/step-registry.ts,lib/steps/index.ts), updated action labels, and integration types to include Apify.New UI Components
TemplateBadgeJsoncomponent for real-time JSON validation and formatting in action configuration.