STEP 1
Connect Apify and Rundeck
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Apify and Rundeck Integration
Keep Apify and Rundeck in sync by integrating their events and actions. When developer tools events happen in Apify, update the Rundeck automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Rundeck
Detailed info you need to know about Apify and Rundeck integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to Rundeck
Set up your Apify and Rundeck integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and Rundeck nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Apify and Rundeck. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and Rundeck work in WEXTL?
WEXTL exposes actions and triggers for Apify and Rundeck that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Apify triggersRundeck actions
Apify modules
- Add Request to QueueCreates request to queue.
- Batch Add RequestsPerforms batch add requests.
- Build ActorBuilds actor.
- Charge Events in RunCharges events in run.
- Create ActorCreates actor.
- Create DatasetCreates dataset.
- Create Environment VariableCreates environment variable.
- Create Key-Value StoreCreates key-value store.
- Create Request QueueCreates request queue.
- Create ScheduleCreates schedule.
- Create TaskCreates task.
- Create VersionCreates version.
- Decode and Verify DataRetrieves decode and verify data.
- Delete ActorDeletes actor.
- Delete Build (Abort)Aborts build.
- Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
- Delete DatasetDeletes dataset.
- Delete Environment VariableDeletes environment variable.
- Delete Key-Value StoreDeletes key-value store.
- Delete RecordDeletes record.
- Delete RequestDeletes request.
- Delete Request QueueDeletes request queue.
- Delete Run (Abort)Aborts an Actor run (DELETE semantics).
- Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
- Delete ScheduleDeletes schedule.
- Delete TaskDeletes task.
- Delete VersionDeletes version.
- Delete WebhookDeletes webhook.
- Download Records (Batch Export)Retrieves download records (batch export).
- Encode and Sign DataEncodes and sign data.
- Get ActorReturns actor.
- Get Browser InfoReturns browser info.
- Get Browser Info (POST Variant)Returns browser info (post variant).
- Get BuildReturns build.
- Get Build (Cross-Actor)Returns build (cross-actor).
- Get Build LogReturns build log.
- Get Build Log (Cross-Actor)Returns build log (cross-actor).
- Get DatasetReturns dataset.
- Get Dataset ItemsReturns dataset items.
- Get Dataset StatisticsReturns dataset statistics.
- Get Default BuildReturns default build.
- Get Environment VariableReturns environment variable.
- Get Environment VariablesReturns environment variables.
- Get Key-Value StoreReturns key-value store.
- Get Last Task RunReturns last task run.
- Get List of ActorsReturns list of actors.
- Get List of BuildsReturns list of builds.
- Get List of DatasetsReturns list of datasets.
- Get List of Key-Value StoresReturns list of key-value stores.
- Get List of KeysReturns list of keys.
Rundeck modules
- Abort ExecutionAborts execution.
- Browse Job GroupsBrowses job groups.
- Bulk Disable ExecutionsPerforms the disable Executions operation.
- Bulk Disable SchedulesPerforms the disable Schedules operation.
- Bulk Enable ExecutionsPerforms the enable Executions operation.
- Bulk Enable SchedulesPerforms the enable Schedules operation.
- Create ProjectCreates a project.
- Create Project ACLCreates a project acl.
- Create System ACLCreates a system acl.
- Create TokenCreates a token.
- Create User TokenCreates an user token.
- Create WebhookCreates a webhook.
- Create/Import JobsCreates a /import jobs.
- Delete All Job ExecutionsDeletes all job executions.
- Delete Config KeyDeletes config key.
- Delete ExecutionDeletes execution.
- Delete Executions BulkDeletes executions bulk.
- Delete JobDeletes job.
- Delete Job Executions HistoryDeletes job executions history.
- Delete Jobs BulkDeletes jobs bulk.
- Delete Jobs FileDeletes jobs file.
- Delete KeyDeletes key.
- Delete MOTDDeletes motd.
- Delete Named Project ACLDeletes named project acl.
- Delete Named System ACLDeletes named system acl.
- Delete ProjectDeletes project.
- Delete Project ACLDeletes project acl.
- Delete ReadmeDeletes readme.
- Delete System ACLDeletes system acl.
- Delete TokenDeletes token.
- Delete WebhookDeletes webhook.
- Disable Job ExecutionDisables job execution.
- Disable Job ScheduleDisables job schedule.
- Disable System ExecutionsDisables system executions.
- Enable Job ExecutionEnables job execution.
- Enable Job ScheduleEnables job schedule.
- Enable System ExecutionsEnables system executions.
- Execute Bulk Execution DeleteExecutes bulk execution delete.
- Execute Bulk Job DeleteExecutes bulk job delete.
- Export JobsRetrieves export jobs.
- Export ProjectExports project.
- Export Project AsyncExports project async.
- Get ExecutionReturns execution.
- Get Execution MetricsReturns execution metrics.
- Get Execution ModeReturns execution mode.
- Get Execution OutputReturns execution output.
- Get Execution Output NodeReturns execution output node.
- Get Execution Output StateReturns execution output state.
- Get Execution Output StepReturns execution output step.
- Get Execution Result DataReturns execution result data.
Frequently asked questions
Common questions about connecting Apify and Rundeck.
Connect your Apify and Rundeck accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Apify's "Watch Run Aborted" fires, WEXTL can "Abort Execution" in Rundeck. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); Rundeck has 141 actions (including Abort Execution, Browse Job Groups, and Bulk Disable Executions). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Apify-to-Rundeck automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Apify (or Rundeck) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Apify + Rundeck automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Apify and Rundeck integration.
- Apify and Rundeck integration source code, module specs and credentials implementation.
- Our Apify and Rundeck integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Rundeck — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Apify integration information
- Rundeck integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library