See llms.txt for all machine-readable content.

AWS Lambda and Slack integration

Save yourself the work of writing custom integrations for AWS Lambda and Slack and use n8n instead. Build adaptable and scalable Development, workflows that work with your technology stack. All within a building experience you will love.

How to connect AWS Lambda and Slack

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

AWS Lambda and Slack integration: Create a new workflow and add the first step

Detect AWS Orphaned Resources & Send Cost Reports to Slack, Email, and Sheets

How it works This workflow automatically scans AWS accounts for orphaned resources (unattached EBS volumes, old snapshots >90 days, unassociated Elastic IPs) that waste money. It calculates cost impact, validates compliance tags, and sends multi-channel alerts via Slack, Email, and Google Sheets audit logs. Key Features: 🔍 Multi-region scanning with parallel execution 💰 Monthly/annual cost calculation with risk scoring 📊 Professional HTML reports with charts and tables 🏷️ Tag compliance validation (SOC2/ISO27001/HIPAA) ✅ Conditional alerting (only alerts when resources found) 📈 Google Sheets audit trail for trend analysis What gets detected: Unattached EBS volumes ($0.10/GB/month waste) Snapshots older than 90 days ($0.05/GB/month) Unassociated Elastic IPs ($3.60/month each) Typical savings: $50-10K/month depending on account size Set up steps Prerequisites AWS Configuration: Create IAM user n8n-resource-scanner with these permissions: ec2:DescribeVolumes ec2:DescribeSnapshots ec2:DescribeAddresses ec2:DescribeInstances lambda:InvokeFunction Deploy Lambda function aws-orphaned-resource-scanner (Node.js 18+) Add EC2 read-only permissions to Lambda execution role Generate AWS Access Key + Secret Key Lambda Function Code: See sticky notes in workflow for complete implementation using @aws-sdk/client-ec2 Credentials Required: AWS IAM (Access Key + Secret) Slack (OAuth2 or Webhook) Gmail (OAuth2) Google Sheets (OAuth2) Configuration Initialize Config Node: Update these settings: awsRegions: Your AWS regions (default: us-east-1) emailRecipients: FinOps team emails slackChannel: Alert channel (e.g., #cloud-ops) requiredTags: Compliance tags to validate snapshotAgeDays: Age threshold (default: 90) Set Region Variables: Choose regions to scan Lambda Function: Deploy function with provided code (see workflow sticky notes) Google Sheet: Create spreadsheet with headers: Scan Date | Region | Resource Type | Resource ID | Monthly Cost | Compliance | etc. Credentials: Connect all four credential types in n8n Schedule: Enable "Weekly Scan Trigger" (default: Mondays 8 AM UTC) Testing Click "Execute Workflow" to run manual test Verify Lambda invokes successfully Check Slack alert appears Confirm email with HTML report received Validate Google Sheets logging works Customization Options Multi-region: Add regions in "Initialize Config" Alert thresholds: Modify cost/age thresholds Additional resource types: Extend Lambda function Custom tags: Update required tags list Schedule frequency: Adjust cron trigger Use Cases FinOps Teams: Automated cloud waste detection and cost reporting Cloud Operations: Weekly compliance and governance audits DevOps: Resource cleanup automation and alerting Security/Compliance: Tag validation for SOC2/ISO27001/HIPAA Executive Reporting: Monthly cost optimization metrics Resources AWS IAM Best Practices Lambda Function Code

Popular ways to use the AWS Lambda and Slack integration

Build your own AWS Lambda and Slack integration

Create custom AWS Lambda and Slack workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

AWS Lambda supported actions

Invoke

Invoke a function

Slack supported actions

AWS Lambda and Slack integration details

AWS Lambda

AWS Lambda

AWS Lambda is a tool that helps you run codes without having to worry about servers, clusters, provisioning or managing infrastructure. With this tool, you can respond to high demand, save money by only paying for the compute time you use, and much more benefits.

Slack

Slack

Slack is a powerful collaboration tool for businesses of all sizes. It brings team communication and collaboration into one place so you can get more work done, whether you belong to a large enterprise or a small business.

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQ about AWS Lambda integrations

Need help setting up your AWS Lambda and Slack integration?

Discover our latest community's recommendations and join the discussions about AWS Lambda and Slack integration.

  • Michelle

    Slack node: Channel list not loading with "Issues: There was a problem loading the parameter options from server: "[object Object]""

    Michelle

    I’m trying to use a Slack node for searching messages in a specific channel. Yet, when I add the option for channel selection, I get an error: *Issues: There was a problem loading the parameter options from server: “[ob…

    Open topic
  • Ageng Putra

    Slack Trigger Node stopped working between two different channels

    Ageng Putra

    Describe the problem/error/question I have two separate workflows, each using a different Slack app integration: Staging channel → uses trigger-app 1 Production channel → uses trigger-app 2 The issue: The Slack…

    Open topic
  • Kyrylo

    Slack's channel history timestamp parameters

    Kyrylo

    Describe the problem I’m trying to get certain messages from a channel. The way I had it configured with HTTP node was by making a request to this URL: https://slack.com/api/conversations.history?channel={{ $(‘get_all_m…

    Open topic
  • Ignas

    Scalable Slack triggers set up

    Ignas

    Describe the problem/error/question Hey Community, we recently rolled out N8N company wide and we are missing is scalable solution to Slack trigger set up. The problem is that for every workflow that we create in N8N we …

    Open topic
  • Sergiy B.

    Slack node token rotation issue

    Sergiy B.

    Describe the problem/error/question I have a Opt in option switched on in the Slack app, so tokens are rotating every 12 hours, but there is no way I found in n8n to make dynamik access tocken to be applied, so every 12…

    Open topic

Looking to integrate Slack and VirusTotal in your company?

Trusted by teams building smarter workflows.

Why

Why use n8n to integrate AWS Lambda with Slack

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship