AWS Lambda and BugBug Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between AWS Lambda and BugBug on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about AWS Lambda and BugBug

Detailed info you need to know about AWS Lambda and BugBug integrations in WEXTL. Explore which modules apps support and how you connect them.

  • AWS Lambda

    • Developer Tools
    • 1 trigger
    • 38 searches
    • 49 actions

    Serverless compute that runs your code without managing servers.[5]

  • BugBug

    • Developer Tools
    • 3 triggers
    • 51 searches
    • 50 actions

    No-code browser test automation for web apps.[6]

How to connect AWS Lambda to BugBug

Set up your AWS Lambda and BugBug integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between AWS Lambda and BugBug work in WEXTL?

WEXTL exposes actions and triggers for AWS Lambda and BugBug that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

AWS Lambda triggersBugBug actions

AWS Lambda modules

  • Watch Durable Executions Polls a function and fires once for every durable execution that began since the previous check. Use Status to watch only one state, and Limit for how many the first check emits.
  • Add a Function Permission Lets another service, account or role use a function by adding a statement to its resource policy. Use Action and Principal to say who may do what, and Source ARN to limit it to one calling resource.
  • Add a Layer Version Permission Shares a layer version with an account by adding a policy statement. Use Principal * with Organization ID to open it to one organization, and Revision ID to skip the change if the policy moved on since you read it.
  • Add Tags to a Resource Attaches Tags to the resource behind the Resource ARN. A tag whose key already exists gets the new value.
  • Cancel a Durable Execution Stops a durable execution. Use Error Message to record why it was stopped, and Error Type, Error Data or Stack Trace to attach error details. Output is the Stop Timestamp.
  • Create a Capacity Provider Sets up a capacity provider that runs functions on compute instances in your own subnets. It needs VPC Config and Permissions Config. Use Scaling Config to set how it scales and Instance Requirements to limit the instance types.
  • Create a Code Signing Config Defines which signing profiles may sign code for functions, through Allowed Publishers. Use Code Signing Policies to decide what happens when a signature check fails.
  • Create a Durable Execution Checkpoint Saves progress of a durable execution against its current Checkpoint Token. Use Updates for state changes such as completing a step or starting a wait. Output includes the next Checkpoint Token.
  • Create a Function Deploys a new Lambda function under a Role, from your Code. For zip packages add a Runtime and Handler, and for container images an image URI. Use Timeout and Memory Size to replace the defaults of 3 seconds and 128 MB.
  • Create a Function URL Config Gives a function a dedicated HTTPS endpoint. Use Auth Type to choose between AWS IAM and open access, Invoke Mode for buffered or streamed answers, and Cors for cross-origin rules.
  • Create an Alias Adds a named alias that points to a version of a function. Use Routing Config to send a share of the traffic to a second version.
  • Create an Event Source Mapping Connects a function to a stream, queue or broker and has records delivered in batches. Use Event Source ARN for a Kinesis or DynamoDB stream, an SQS queue or another source, and Batch Size to bound each batch.
  • Delete a Capacity Provider Removes a capacity provider from the account and returns its final Capacity Provider record.
  • Delete a Code Signing Config Deletes a code signing config from your Lambda account.
  • Delete a Function Deletes a function. Use Qualifier to delete a single version, otherwise the function goes with all of its versions and aliases.
  • Delete a Function Code Signing Config Unlinks a function from the code signing config that it was bound to.
  • Delete a Function Concurrency Clears the reserved concurrency set on a function.
  • Delete a Function Event Invoke Config Removes the retry and destination settings for asynchronous calls. Use Qualifier to target a version or alias, or leave it empty for the latest version.
  • Delete a Function URL Config Removes the HTTPS endpoint of a function, or of one alias when Qualifier names it.
  • Delete a Layer Version Deletes a numbered version of a layer from Lambda.
  • Delete a Provisioned Concurrency Config Removes the warm capacity set on one version or alias, chosen with Qualifier.
  • Delete a Resource Policy Removes the policy that sits on a function or layer version. Use Revision ID to delete only if the current revision matches, or leave it empty to delete regardless.
  • Delete an Alias Deletes one alias of a function by its name.
  • Delete an Event Source Mapping Removes the link between a function and its stream, queue or broker. The final mapping settings are returned.
  • Get a Capacity Provider Looks up a capacity provider and returns its full Capacity Provider record.
  • Get a Code Signing Config Retrieves a code signing config, including its allowed publishers and policy, as Code Signing Config.
  • Get a Durable Execution Shows the status of one durable execution with its start and end timestamps. Turn off Include Execution Data to leave out the input, result and error and get a smaller response.
  • Get a Durable Execution History Lists the events recorded for a durable execution, such as when it started, succeeded or failed. Use Newest First to reverse the order, and Include Execution Data to turn step results and callback payloads on or off.
  • Get a Durable Execution State Returns the operations of a durable execution as of a given Checkpoint Token, with the Status and details of each step, wait or callback. Use Limit to bound a run.
  • Get a Function Returns a function in full, with its Configuration, Code details and Tags. Add a Qualifier to read one version or alias, and expect environment variable values in the output.
  • Get a Function Code Signing Config Checks which code signing config is attached to a function and returns its Code Signing Config ARN.
  • Get a Function Concurrency Looks up how many concurrent executions are reserved for a function, as Reserved Concurrent Executions.
  • Get a Function Configuration Pulls the settings of a function, such as its Runtime, Handler, Timeout and Memory Size, without the code details. Add a Qualifier to pick a version or alias, and environment variable values are included.
  • Get a Function Event Invoke Config Reads how a function handles asynchronous calls: Maximum Retry Attempts, Maximum Event Age In Seconds and the Destination Config.
  • Get a Function Policy Returns the resource-based policy of a function as Policy, along with its Revision ID for later guarded changes.
  • Get a Function Recursion Config Shows what Lambda does with a function that calls itself in a loop, as the Recursive Loop setting.
  • Get a Function Scaling Config Returns the Applied Function Scaling Config and the Requested Function Scaling Config of a given version or alias.
  • Get a Function URL Config Reads the function URL configuration of a function. Output includes the Function URL, Auth Type, Invoke Mode and Cors.
  • Get a Layer Version Retrieves one version of a layer, its Description, Compatible Runtimes and License Info, plus a Content location.
  • Get a Layer Version by ARN Looks up a layer version from its full Layer Version ARN, including its Description, Compatible Runtimes and License Info.
  • Get a Layer Version Policy Returns the permissions granted on a layer version as Policy, together with its Revision ID.
  • Get a Provisioned Concurrency Config Checks warm capacity of a function alias or version. It compares Requested Provisioned Concurrent Executions with Available Provisioned Concurrent Executions and gives the Status.
  • Get a Resource Policy Reads the access policy of a Lambda function or layer version, found from its Resource ARN. Output includes the Policy and Revision ID.
  • Get a Runtime Management Config Shows how a function picks up runtime updates through Update Runtime On, along with its Runtime Version ARN.
  • Get Account Settings Reads the Lambda limits for your account together with how much of them is in use, as Account Limit and Account Usage.
  • Get an Alias Fetches an alias of a function, giving the version it points to, its Routing Config and its Revision ID.
  • Get an Event Source Mapping Reads the settings of a mapping between a function and an event source, such as its Batch Size and Starting Position.
  • Invoke a Function Runs a Lambda function with a JSON Payload as its input, up to 6 MB. Use Invocation Type to wait for the result or return at once, and Qualifier to run a version or alias. Turn off Stop On Function Error to branch on failures.
  • List Aliases Shows the aliases of one function, each with its Name, Function Version and Routing Config. Use Function Version to keep only aliases that point to one version.
  • List Capacity Providers Lists the capacity providers of your account along with their State and VPC Config. Use State to keep only providers in one state.

BugBug modules

  • Check a Project Import Tests a project export File against BugBug before importing it. Reports whether it is Valid along with a Summary of its content.
  • Check a Test Import Looks over a test File and reports if it is Valid, with a Summary, without creating anything.
  • Create a Component Adds a reusable block of steps that tests can share. Give it a Name and switch Is Active to run it.
  • Create a Folder Makes a folder of a given Kind for organizing items. Set Parent ID to nest it inside another folder.
  • Create a Group Adds a group of steps to a test. Use At Index to place it, Is Component to make it a reusable component and Folder ID to file that component in a folder.
  • Create a Step Adds one action to a group, with a Type and optional Position or Name. Fill Step Fields (JSON) with the parameters of that action.
  • Create a Suite Creates a suite of tests that run together under a Run Profile ID. Set Run In Parallel to run its tests side by side, Auto Retry to retry failed tests and Auto Add New Tests to include every new test in it.
  • Create a Tag Creates a tag, using Color for its hex value and Project ID to place it in a specific project rather than the one tied to the token.
  • Create a Test Makes a browser test and keeps its Notes. Use Screen Size Type to run it on desktop, mobile or a custom screen, Folder ID to file it and Tag Names to tag it.
  • Create a Variable Defines a variable by Key and Type, with an optional Value. Turn on Is Secret to hide the value in BugBug.
  • Delete a Folder Removes a folder. Turn on Force to delete it even when it has content.
  • Delete a Group Deletes a group of steps from a test.
  • Delete a Project File Removes one uploaded file from a BugBug project.
  • Delete a Reference Screenshot Deletes a stored baseline image that visual comparison relies on.
  • Delete a Step Removes one action from a test.
  • Delete a Suite Deletes a suite of tests from your project.
  • Delete a Tag Removes a label from your project.
  • Delete a Test Removes a test from your BugBug project.
  • Delete Project Files in Bulk Deletes many project Files in one call and reports how many Steps Affected used them.
  • Detach a Component from a Test Turns a component used by a test into ordinary steps of that test, so edits no longer touch the shared block.
  • Download a Project Backup Downloads one saved Backup of a project as a file, with its File Name and Content Type.
  • Download a Project File Fetches the content of an uploaded project file as a File with its File Name and Content Type.
  • Download a Suite Run JUnit Report Gets the JUnit XML report of a finished suite run for use in CI tools.
  • Download a Test Run JUnit Report Gets the JUnit XML report of a single test run, which CI tools can read.
  • Download Test Run Logs Downloads the log file of one test run with its File Name and Content Type.
  • Export a Project as ZIP Packs the whole BugBug project into a ZIP file, which you can import elsewhere.
  • Export a Test as YAML Returns the full definition of a test, written as YAML text.
  • Export a Test as ZIP Packs a test with what it needs into a ZIP file for import elsewhere, with step passwords removed.
  • Get a Folder Reads one folder with its Name, Kind, Depth and Parent ID.
  • Get a Group Reads a step group with its Name, Is Component flag and Folder ID.
  • Get a Project File Pulls the record of an uploaded file with Extension, Size and URL, but not its bytes.
  • Get a Reference Screenshot Reads one baseline image record with its Screenshot URL and Browser Name.
  • Get a Run Profile Shows a run profile with its Name and whether it Is Default for new runs.
  • Get a Step Reads one step with its Type, Name and Group ID.
  • Get a Step Run Looks up how one step went in a test run, with its Status and Test Run ID.
  • Get a Suite Reads a suite, including Auto Retry, Before After All Enabled and Auto Add New Tests.
  • Get a Suite Run Loads a suite run with its Duration, Ended time and Error Code.
  • Get a Tag Returns one tag with its Color and Name. Pass a Project ID when the tag belongs to another project.
  • Get a Test Fetches a test with its Name, Tags and the Groups of steps.
  • Get a Test Run Pulls a test run with the Browser Name, Browser Version and Duration.
  • Get a Test Run Debug Artifact Retrieves one debugging file of a test run, by its Artifact Kind, with its File and Content Type.
  • Get a Variable Reads one variable by Variable Key, with its Value, Type and whether it Is Secret.
  • Get Component Usage Finds which tests use a component, returned as Usage and the Tests Ids.
  • Get Project File Usage Finds where an uploaded file is used and reports the Steps Count plus the Tests that reference it.
  • Get Project Settings Shows the defaults of your project, including Browser Width, Browser Height, Browser Language and the Initial Run Profile ID.
  • Get Suite Run Screenshots Pulls the screenshots taken during a suite run, grouped as Tests Runs.
  • Get Suite Run Status Checks how far a suite run has come, showing Status and Finished Tests.
  • Get Test Run Screenshots Pulls the screenshots taken during a test run, grouped as Steps Runs.
  • Get Test Run Status Checks how far a test run has come, showing Status and Finished Steps.
  • Get the API Status Checks that BugBug is reachable and says whether you are Authenticated.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with AWS Lambda and BugBug integrations. Pick any from the list below if the current combination isn't the one you need.

Automate AWS Lambda and BugBug on WEXTL®

Claim your 3-day trial to build AWS Lambda with BugBug integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Lambda and BugBug.

How do I connect AWS Lambda and BugBug?

Connect your AWS Lambda and BugBug 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]

What can I automate between AWS Lambda and BugBug?

Example: when the "Watch Durable Executions" trigger in AWS Lambda fires, WEXTL can "Check a Project Import" in BugBug. AWS Lambda has 1 trigger (including Watch Durable Executions). BugBug has 101 actions (including Check a Project Import, Check a Test Import, and Create a Component). Add filters and transforms between steps when you need them.[1]

Can AWS Lambda trigger actions in BugBug, and BugBug in AWS Lambda?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate AWS Lambda and BugBug?

No. AWS Lambda-to-BugBug automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does AWS Lambda integrate with BugBug in real time?

Yes. Trigger-based automations start the moment AWS Lambda (or BugBug) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a AWS Lambda + BugBug integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect AWS Lambda with BugBug?

You can build your AWS Lambda + BugBug automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the AWS Lambda and BugBug integration.

  1. AWS Lambda and BugBug integration source code, module specs and credentials implementation.
  2. Our AWS Lambda and BugBug integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Lambda and BugBug, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. AWS Lambda integration information
  6. BugBug integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted AWS Lambda and BugBug integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Lambda and BugBug, or get started