STEP 1
Connect AWS Lambda and Bright Data
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
AWS Lambda and Bright Data Integration
Keep AWS Lambda and Bright Data in sync by integrating their events and actions. When developer tools events happen in AWS Lambda, update the Bright Data 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 AWS Lambda and Bright Data
Detailed info you need to know about AWS Lambda and Bright Data integrations in WEXTL. Explore which modules apps support and how you connect them.
AWS Lambda
Serverless compute that runs your code without managing servers. [5]
Bright Data
Web scraping, data collection, and proxy infrastructure for accessing blocked websites and curated marketplace datasets. [6]
How to connect AWS Lambda to Bright Data
Set up your AWS Lambda and Bright Data integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AWS Lambda and Bright Data 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 AWS Lambda and Bright Data. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AWS Lambda and Bright Data work in WEXTL?
WEXTL exposes actions and triggers for AWS Lambda and Bright Data 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.
AWS Lambda triggersBright Data actions
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.
Bright Data modules
- Add ZoneCreates a new Bright Data zone (SERP, Scraping Browser, Residential, Mobile, ISP, or Datacenter proxy). Requires Admin or Ops role.
- Cancel SnapshotCancel Snapshots a running or paused Web Scraper snapshot.
- Cancel Studio JobPermanently stops a Scraper Studio job. The job moves to canceled and cannot be resumed.
- Crawl (Studio)Runs a synchronous real-time Scraper Studio scrape, holding the request open until it finishes or the timeout is reached.
- Delete ZonePermanently removes a Bright Data zone. Requires Admin or Ops role.
- Deliver Marketplace SnapshotShips a completed Marketplace Dataset API snapshot to a webhook, S3, GCS, Azure, Ali OSS, or other supported destination.
- Deliver SnapshotShips a completed Web Scraper snapshot to a webhook, S3, GCS, Azure, SFTP, or Snowflake destination.
- Download Marketplace SnapshotDownloads the records from a completed Marketplace Dataset API snapshot, optionally by part for large results.
- Download SnapshotDownloads the records from a completed Web Scraper snapshot, optionally by part for large results.
- Filter Marketplace DatasetRuns an async filter job (snapshot-based) against any of Bright Data's 250+ Marketplace datasets and returns a snapshot_id to download once the job completes. Same filter/operator syntax as Search.
- Get Customer BalanceReads your account's current credit balance.
- Get Dataset MetadataReturns field names, types, and descriptions for a Marketplace dataset — use this to discover filterable field names before calling Search or Filter.
- Get Delivery Destination SchemaReturns the exact fields and credentials Bright Data requires to configure a specific delivery destination type (S3, SFTP, GCS, webhook, and others).
- Get Marketplace Snapshot MetadataReturns status and size metadata for a Marketplace Dataset API snapshot (from Filter Marketplace Dataset, Trigger Collection, or a dataset subscription).
- Get Marketplace Snapshot PartsReturns the number of delivery parts for a Marketplace Dataset API snapshot — call before Download Marketplace Snapshot for a large result.
- Get Snapshot InputReturns the input array a snapshot was triggered with.
- Get Snapshot LogReturns the job log for a snapshot.
- Get Snapshot PartsReturns the number of delivery parts and per-part metadata for a snapshot.
- Get Studio DatasetDownloads the records produced by a Scraper Studio batch collection.
- Get Studio Job ErrorsReturns per-input error details for a Scraper Studio batch job.
- Get Studio Job LogReturns job metadata for a Scraper Studio job: status, input/output counts, failures, and run timestamps.
- Get Studio Job ResultFetches the result of a real-time Scraper Studio scrape by response ID.
- Get View Delivery SettingsRetrieves the current delivery configuration for a Marketplace dataset view — destination, credentials, filename, compression and batch size.
- Get Zone ConfigReads the configuration of a single zone.
- List Active ZonesLists the currently active zones in your account.
- List All ZonesLists every zone in your account, including inactive ones.
- List CountriesLists the country codes available for proxy targeting on your account.
- List Delivery Destination TypesLists the delivery destination types Bright Data supports for dataset view delivery (webhook, S3, GCS, Azure, and others).
- List Marketplace DatasetsLists every Bright Data Marketplace dataset available on your account, with id, name, and record count.
- List ScrapersLists the Web Scraper scrapers available in your account.
- List SnapshotsLists your Web Scraper collection snapshots, optionally filtered by dataset or status.
- List Studio JobsLists Scraper Studio jobs in a date range, optionally filtered to one scraper.
- List Studio ScrapersLists the Scraper Studio scrapers in your account, with active status and output schema.
- List ViewsLists your Marketplace dataset views — saved, filtered subscriptions that deliver fresh records to a destination on a recurring schedule.
- Make an API CallPerforms an arbitrary authorized API call to the Bright Data API.
- Monitor DeliveryPolls the status of a Deliver Snapshot job until it completes.
- Monitor Job ProgressReads the status and progress of an async collection job.
- Pause SnapshotPause Snapshots a running or paused Web Scraper snapshot.
- Pause Studio JobTemporarily stops a running Scraper Studio job. The job moves to paused and can be resumed later.
- Rerun SnapshotReruns a Web Scraper snapshot, returning a new snapshot ID.
- Rerun Studio JobStarts a new run from an existing Scraper Studio job, either in full or failed-inputs-only, returning a new collection ID.
- Resume SnapshotResumes a paused Web Scraper snapshot.
- Scrape URL (Sync)Runs a real-time synchronous scrape for a supported dataset and returns records inline, or falls through to a pending snapshot if the 60-second vendor timeout is hit.
- Search Marketplace DatasetRuns a real-time, Elasticsearch-powered filter query against a Bright Data Marketplace dataset and returns matching records inline with sub-second latency (up to 1,000 per call). Alpha — 3 LinkedIn datasets only.
- Send SERP SearchFetches structured Google/Bing/Yandex/DuckDuckGo search results through Bright Data's SERP API.
- Send Web RequestFetches a URL through Bright Data's Web Unlocker, bypassing anti-bot protection and CAPTCHAs.
- Trigger Collection (Async)Starts an asynchronous Web Scraper collection job and returns a snapshot ID to monitor and download later.
- Trigger Studio Scraper (Batch)Starts an asynchronous batch collection for a Scraper Studio scraper and returns a collection ID.
- Trigger Studio Scraper (Real-time)Starts an asynchronous real-time Scraper Studio scrape and returns a response ID to fetch the result later.
- Update View Delivery SettingsReplaces the delivery destination, credentials, filename template and batch/packaging options for a single Marketplace dataset view.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with AWS Lambda and Bright Data integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting AWS Lambda and Bright Data.
Connect your AWS Lambda and Bright Data 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 AWS Lambda's "Watch Durable Executions" fires, WEXTL can "Add Zone" in Bright Data. AWS Lambda has 1 trigger (including Watch Durable Executions); Bright Data has 50 actions (including Add Zone, Cancel Snapshot, and Cancel Studio Job). 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. AWS Lambda-to-Bright Data 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 AWS Lambda (or Bright Data) 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 AWS Lambda + Bright Data 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 AWS Lambda and Bright Data integration.
- AWS Lambda and Bright Data integration source code, module specs and credentials implementation.
- Our AWS Lambda and Bright Data integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Lambda and Bright Data — 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.
- AWS Lambda integration information
- Bright Data integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library