STEP 1
Connect Apify and AWS Lambda
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 AWS Lambda Integration
Connect Apify and AWS Lambda to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and AWS Lambda
Detailed info you need to know about Apify and AWS Lambda integrations in WEXTL. Explore which modules apps support and how you connect them.
Apify
Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events. [5]
AWS Lambda
Serverless compute that runs your code without managing servers. [6]
How to connect Apify to AWS Lambda
Set up your Apify and AWS Lambda integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and AWS Lambda 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 AWS Lambda. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and AWS Lambda work in WEXTL?
WEXTL exposes actions and triggers for Apify and AWS Lambda 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 triggersAWS Lambda 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 KeysReturns list of keys.
- Get List of Key-Value StoresReturns list of key-value stores.
AWS Lambda modules
- Add Function PermissionGrants another account or service permission to use a function.
- Add Layer Version PermissionLets another account or organization use a layer version.
- Add Tags to ResourceAdds tags to a function, alias, layer, mapping or similar resource.
- Cancel Durable ExecutionStops a running durable execution.
- Create AliasCreates a named pointer to a function version.
- Create Capacity ProviderCreates a capacity provider for Lambda Managed Instances.
- Create Code Signing ConfigCreates a code signing config.
- Create Durable Execution CheckpointSaves progress for a durable execution.
- Create Event Source MappingConnects an event source (queue, stream, topic) to a function.
- Create FunctionCreates a new function.
- Create Function URL ConfigCreates a public HTTPS endpoint for a function.
- Delete AliasDeletes an alias.
- Delete Capacity ProviderDeletes a capacity provider.
- Delete Code Signing ConfigDeletes a code signing config.
- Delete Event Source MappingDeletes an event source mapping.
- Delete FunctionDeletes a function or one version of it.
- Delete Function Code Signing ConfigDetaches the code signing config from a function.
- Delete Function ConcurrencyRemoves the reserved concurrency from a function.
- Delete Function Event Invoke ConfigRemoves the async-invoke settings.
- Delete Function URL ConfigRemoves a function URL.
- Delete Layer VersionDeletes a layer version.
- Delete Provisioned Concurrency ConfigRemoves provisioned concurrency.
- Delete Resource PolicyRemoves the resource-based policy.
- Get Account SettingsReturns the Region's limits and usage.
- Get AliasReturns one alias.
- Get Capacity ProviderReturns one capacity provider.
- Get Code Signing ConfigReturns one code signing config.
- Get Durable ExecutionReturns one durable execution.
- Get Durable Execution HistoryRetrieves the event history of a durable execution.
- Get Durable Execution StateRetrieves the saved state of a durable execution.
- Get Event Source MappingReturns one event source mapping.
- Get FunctionReturns a function's configuration, code location, tags and concurrency.
- Get Function Code Signing ConfigReturns the code signing config attached to a function.
- Get Function ConcurrencyReturns the reserved concurrency.
- Get Function ConfigurationReturns only a function's settings.
- Get Function Event Invoke ConfigReturns the async-invoke settings (retries, max event age, destinations).
- Get Function PolicyReturns a function's resource policy.
- Get Function Recursion ConfigReturns whether recursive loops are allowed for a function.
- Get Function Scaling ConfigReturns the applied and requested scaling settings.
- Get Function URL ConfigReturns a function's URL settings.
- Get Layer VersionReturns one version of a layer, including its download link.
- Get Layer Version By ARNReturns a layer version found by its ARN.
- Get Layer Version PolicyReturns a layer version's resource policy.
- Get Provisioned Concurrency ConfigReturns requested/available/allocated provisioned concurrency and status.
- Get Resource PolicyReturns the resource-based policy of a function or layer version ARN.
- Get Runtime Management ConfigReturns how a function's runtime is updated.
- Invoke FunctionRuns a Lambda function and returns what it sends back.
- List AliasesRetrieves a list of aliases of a function.
- List Capacity ProvidersRetrieves a list of capacity providers.
- List Code Signing ConfigsRetrieves a list of code signing configs.
Frequently asked questions
Common questions about connecting Apify and AWS Lambda.
Connect your Apify and AWS Lambda 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 "Add Function Permission" in AWS Lambda. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); AWS Lambda has 87 actions (including Add Function Permission, Add Layer Version Permission, and Add Tags to Resource). 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-AWS Lambda 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 AWS Lambda) 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 + AWS Lambda 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 AWS Lambda integration.
- Apify and AWS Lambda integration source code, module specs and credentials implementation.
- Our Apify and AWS Lambda integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and AWS Lambda — 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
- AWS Lambda integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library