AWS Lambda and Updown.io Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect AWS Lambda and Updown.io 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 trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS Lambda and Updown.io
Detailed info you need to know about AWS Lambda and Updown.io 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]
Updown.io

Website uptime monitoring with checks, alerts, status pages and downtime reports.[6]
How to connect AWS Lambda to Updown.io
Set up your AWS Lambda and Updown.io integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect AWS Lambda and Updown.io
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected AWS Lambda and Updown.io 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 Updown.io. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between AWS Lambda and Updown.io work in WEXTL?
WEXTL exposes actions and triggers for AWS Lambda and Updown.io 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 triggersUpdown.io 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.
Updown.io modules
- Create a Check Starts monitoring a URL or a heartbeat with updown.io. Use Period (Seconds) to set how often it runs and Apdex Threshold to set the response time that counts as satisfying.
- Create a Recipient Adds a place to send alerts, such as an email address, a phone number for SMS, or a webhook URL. Use Select on All Checks to attach it to every check you already have.
- Create a Status Page Builds a page that shows the state of several Checks, in the order given. Use Visibility and Access Key to control who can open it.
- Delete a Check Deletes one monitoring check from updown.io. This cannot be undone.
- Delete a Recipient Removes an alert recipient from your updown.io account. A webhook recipient may belong to a workflow trigger.
- Delete a Status Page Removes a published status page. This cannot be undone.
- Get a Check Reads one check with its URL, Uptime, Period and current Down state. Turn on Include Metrics for the last hour of performance figures, or Include Results for the last 5 requests.
- Get Check Metrics Reads Uptime, Apdex, Timings and Requests for one check over a period. Use From and To to set the window and Group By to split the totals.
- List Check Downtimes Finds each outage of one check with its Started At, Ended At and Duration (Seconds). Turn on Include Results to add the requests before the downtime and after recovery.
- List Checks Lists every check in your updown.io account with its Token, URL, Alias and Uptime. Use Limit to return fewer rows when you only need a few.
- List Node IP Addresses Lists the IP Address values that updown.io sends its checks from, for firewall allow lists. Use Address Family to get only IPv4 or only IPv6.
- List Nodes Shows the monitoring locations of updown.io with their Code, City and Country. Each row also has IPv4 and IPv6 values for that node.
- List Recipients Gets the alert recipients on your account, each with its ID, Type, Name and Value. Run it to find the ID of a recipient before removing one.
- List Status Pages Retrieves your status pages, each with its Token, Name and Visibility. Checks on every page are included.
- Make an API Call Calls the Updown.io REST API directly with a free-form request under your saved credential.
- Update a Check Edits the URL, Period (Seconds), Apdex Threshold or Enabled setting of an existing check. Alias, String Match and Mute Until change only when filled in.
- Update a Status Page Renames a status page or edits its Description, Visibility and Access Key. Use Checks to replace the whole list of checks it shows.
- Watch Events Starts the workflow the moment updown.io reports a check going down or coming back up. Use the Event, Time and Description values of each alert, plus the Check Alias and Check URL.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with AWS Lambda and Updown.io 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 Updown.io.
References
List of sources used to gather information about the AWS Lambda and Updown.io integration.
- AWS Lambda and Updown.io integration source code, module specs and credentials implementation.
- Our AWS Lambda and Updown.io integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Lambda and Updown.io, 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
- Updown.io integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted AWS Lambda and Updown.io integration page documentation. Used sources, the role of AI, and how the team validates the result.