AWS Lambda and Rootly Integration

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

Build developer tools workflows between AWS Lambda and Rootly 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 Rootly

Detailed info you need to know about AWS Lambda and Rootly 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]

  • Rootly

    • Developer Tools
    • 1 trigger
    • 63 searches
    • 86 actions

    Incident management and on-call platform for detecting, responding to, and learning from incidents.[6]

How to connect AWS Lambda to Rootly

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

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

WEXTL exposes actions and triggers for AWS Lambda and Rootly 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 triggersRootly 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.

Rootly modules

  • Acknowledge an Alert Marks an alert as acknowledged. Use Actor Email to record a specific user as the one who did it, when your organization has actor attribution turned on.
  • Add a Note to an Alert Writes a Note on the activity feed of an alert, credited to the chosen User.
  • Add a Timeline Event to an Incident Writes an Event on the timeline of an incident. Set Visibility to control who can read it.
  • Add Subscribers to an Incident Subscribes the chosen Users to updates on an incident. Turn on Skip Users Without Access to a Private Incident to leave out anyone who cannot see it.
  • Assign a Role to a User on an Incident Gives a user an Incident Role on a single incident and returns the updated incident.
  • Attach Alerts to an Incident Links existing alerts to an incident by their Alert IDs and returns the Incident ID with its Alerts.
  • Cancel an Incident Cancels an incident, with an optional Cancellation Message giving the reason.
  • Create a Cause Adds a cause that incidents and retrospectives can be traced to. Give it a Name, and a Public Name and Public Description for status pages.
  • Create a Functionality Adds a functionality, a capability of your product, from its Name. Link Owner Teams, Owner Users, Environments and Services to show who is behind it.
  • Create a Heartbeat Sets up a heartbeat that alerts when pings stop. Define the Interval with its Interval Unit, an Alert Summary, and who to page through Notification Target Type and Notification Target ID.
  • Create a Pulse Records a pulse from its Summary. Link Services and Environments, and use Labels, References and Data for extra detail.
  • Create a Schedule Creates an on-call schedule from a Name and an Owner. Use Time Zone, Owner Teams and Send Shift Reports to adjust it.
  • Create a Service Registers a service from its Name. Link Owner Teams, Owner Users, Related Services and an Alert Urgency to place it in the rest of your setup.
  • Create a Severity Adds a severity level from a Name. Use Severity Level to rank how serious it is, and Color and Notify Emails to customise it.
  • Create a Status Page Builds a status page titled by Title. Turn Public and Enabled on or off, style it with Header Color and Footer Color, and choose Services and Functionalities to cover.
  • Create a Status Page Announcement Posts an announcement to a status page, from its Title and Body. Turn on Notify Subscribers to alert followers.
  • Create a Sub-Status Adds a sub-status under a Parent Status, from a Name. Use Position to order it among its siblings.
  • Create a Team Forms a responder team called Name. Add Members and Admins, a Color and an Alert Urgency, and switch on Alerts by Email.
  • Create an Action Item Adds a follow-up task to an incident from its Summary. Set a Kind, Priority and Due Date, and name an Assignee or Assigned Teams to own it.
  • Create an Alert Raises an alert from a Summary. Link Services, Teams and Environments, choose an Alert Urgency, and page someone with Notification Target Type and Notification Target ID.
  • Create an Alert Urgency Defines an urgency level from a Name and Description. Use Retrigger After to set how long Rootly waits before alerting again on an unacknowledged alert.
  • Create an Environment Adds an environment such as production, from its Name. Use Notify Emails, Color and External ID to describe and link it.
  • Create an Escalation Policy Builds an escalation policy from a Name. Use Repeat Count to loop it several times, and Teams and Services to attach it.
  • Create an Incident Declares an incident. Add a Title, Severity and Summary, link Services, Environments and Incident Types, and set Private to restrict who can see it.
  • Create an Incident Role Defines a role people can hold during incidents, from a Name. Turn on Optional, Enabled or Allow Several Users to shape it.
  • Create an Incident Type Adds a type for classifying incidents, from a Name. Use Color and Notify Emails to customise it.
  • Create an Override Shift Puts a User on call for a window on a schedule, between Starts At and Ends At in UTC.
  • Delete a Cause Deletes a cause used to classify incidents.
  • Delete a Functionality Removes a functionality, a product capability, from the catalog.
  • Delete a Heartbeat Deletes a heartbeat monitor that expected regular pings.
  • Delete a Schedule Removes an on-call schedule from Rootly.
  • Delete a Service Deletes the chosen service from the Rootly account.
  • Delete a Severity Removes a severity level used for incidents.
  • Delete a Status Page Deletes a customer-facing status page from Rootly.
  • Delete a Status Page Announcement Removes an announcement posted on a status page.
  • Delete a Status Page Event Deletes an incident update that was posted to a status page.
  • Delete a Sub-Status Deletes a sub-status that sits under a parent status.
  • Delete a Team Removes a team from Rootly once Confirm is turned on, because it cannot be undone.
  • Delete an Action Item Deletes an action item from Rootly. Turn on Confirm to go ahead, because it cannot be undone.
  • Delete an Alert Urgency Removes an urgency level that alerts can carry.
  • Delete an Environment Removes an environment from your Rootly catalog.
  • Delete an Escalation Policy Deletes a paging policy from Rootly.
  • Delete an Incident Removes an incident and its record from Rootly.
  • Delete an Incident Role Removes a role that responders can take during incidents.
  • Delete an Incident Timeline Event Deletes one chronology entry from the timeline of an incident.
  • Delete an Incident Type Removes a type used to classify incidents.
  • Delete an Override Shift Deletes a temporary on-call override from a schedule.
  • Detach an Incident from Its Parent Separates a child incident from the parent incident it was grouped under.
  • Escalate an Alert Raises an alert to a higher level of an escalation policy. Name the Escalation Policy and Escalation Policy Level, or leave the level empty for the next one.
  • Get a Cause Looks up a cause with its Slug, Public Name and Position.

Explore alternative integrations

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

Automate AWS Lambda and Rootly on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Lambda and Rootly.

How do I connect AWS Lambda and Rootly?

Connect your AWS Lambda and Rootly 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 Rootly?

Example: when the "Watch Durable Executions" trigger in AWS Lambda fires, WEXTL can "Acknowledge an Alert" in Rootly. AWS Lambda has 1 trigger (including Watch Durable Executions). Rootly has 149 actions (including Acknowledge an Alert, Add a Note to an Alert, and Add a Timeline Event to an Incident). Add filters and transforms between steps when you need them.[1]

Can AWS Lambda trigger actions in Rootly, and Rootly 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 Rootly?

No. AWS Lambda-to-Rootly 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 Rootly in real time?

Yes. Trigger-based automations start the moment AWS Lambda (or Rootly) 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 + Rootly 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 Rootly?

You can build your AWS Lambda + Rootly 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 Rootly integration.

  1. AWS Lambda and Rootly integration source code, module specs and credentials implementation.
  2. Our AWS Lambda and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Lambda and Rootly, 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. Rootly 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 Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Lambda and Rootly, or get started