Skip to main content

Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts

Workflow preview

Workflow preview
100%
Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts preview
Open on n8n.io

1. Workflow Overview

Your automated compliance assistant that pulls, formats, and logs AWS infrastructure evidence to Google Sheets on a recurring schedule. Stop manually exporting IAM user lists and CloudTrail logs fo...

Best for

  • SecOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.awsiam, n8n-nodes-base.if, n8n-nodes-base.googlesheets, n8n-nodes-base.gmail

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mychel Garzon.

Original n8n.io source

1.1 Workflow description

Title
Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts
Workflow name
Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts

Your automated compliance assistant that pulls, formats, and logs AWS infrastructure evidence to Google Sheets on a recurring schedule.

Stop manually exporting IAM user lists and CloudTrail logs for your auditors. This workflow orchestrates the collection of critical infrastructure evidence, validates the data integrity, and appends it to your compliance source of truth automatically. You maintain the cloud; it maintains the proof.

This is not a generic "checklist" template. It is a functional operational pipeline designed to generate empirical evidence for Trust Services Criteria (TSC) compliance.


How the workflow works

The workflow executes in four strategic stages:

  1. Initialize & Schedule: The workflow runs on a quarterly cron schedule (or manual trigger). It initializes the audit metadata, including a precise collection timestamp and the specific Trust Services Criteria (TSC) category being addressed.
  2. Native AWS Extraction: Using the native AWS IAM node, the workflow queries your global identity directory. It fetches the "Get Many" user list, ensuring a clean capture of every active identity currently possessing access to your infrastructure.
  3. Data Normalization: A specialized code node parses the raw AWS response. It extracts critical auditor data—including Usernames, ARNs, and Account Creation Dates—and injects a "Review Required" status to facilitate human-in-the-loop compliance verification.
  4. Evidence Logging & Reporting:
  • Success Path: Evidence is appended to your master Google Sheet. A summarizer node calculates the total user count and fires a professional HTML Executive Summary to your inbox.
  • Failure Path: If authentication fails (e.g., Signature Mismatch) or the directory is empty, a high-priority warning email is sent with specific troubleshooting steps to ensure you never miss a compliance window.

Benefits

  • Auditor-Ready Structure: Does not just dump data; it organizes it by ARN and Creation Date with a built-in "Review Status" column for your compliance team.
  • Self-Healing Logic: Built-in SignatureDoesNotMatch detection. If the AWS connection drops, you get a detailed troubleshooting alert instead of a silent failure.
  • Zero Data Loss: Uses n8n's native credential encryption to securely handle AKIA keys, ensuring your most sensitive infrastructure metadata is never exposed in logs.
  • Eliminates "Audit Panic": By running on a quarterly schedule, you build a continuous trail of evidence, avoiding the 40-hour "last-minute scramble" before the auditor arrives.
  • Executive Visibility: Every run generates a formatted HTML report. You don't have to check a spreadsheet to know you're compliant; you'll see the green "Success" header in your inbox.

Target Audience

  • CTOs & DevOps Leads at startups preparing for their first SOC 2 Type I or Type II audit.
  • Compliance Officers who need an automated "System of Record" for identity access.
  • Security Engineers looking to replace manual AWS exports with immutable, timestamped logs.
  • Managed Service Providers (MSPs) managing compliance for multiple client AWS accounts.

Required APIs

  • AWS IAM Credentials: Access Key (AKIA) and Secret Key with iam:ListUsers permissions.
  • Note: Set region to us-east-1 in n8n credentials.
  • Google Sheets OAuth2: To append evidence to your master compliance spreadsheet.
  • Gmail OAuth2: To deliver the Executive Summary and Failure Alert reports.

Easy Customization

  • Adjust Cadence: Change the Cron expression in the Schedule node to run weekly or monthly for higher-fidelity evidence.
  • Notification Channels: Swap Gmail for Slack, Discord, or Microsoft Teams to fit your team's communication stack.
  • Output Destination: Easily replace Google Sheets with Airtable, PostgreSQL, or Supabase for enterprise-grade data handling.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - README

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note Section 1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note Section 2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note Section 3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note Section 4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Quarterly Schedule

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 7 - Set Audit Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - List IAM Users

Type / Role
n8n-nodes-base.awsIam - awsIam
Config choices
Version 1

Block 9 - Format User Evidence

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - Users Found?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 11 - Export to Google Sheets

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.5

Block 12 - Summarize Run

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 13 - Send Success Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 14 - Send Warning Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

3. Summary Table

Workflow Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts
Complexity intermediate
Nodes 14
Categories SecOps
Author Mychel Garzon
Published 27 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15321/15321.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Collect SOC 2 AWS IAM evidence to Google Sheets with Gmail alerts do?

Your automated compliance assistant that pulls, formats, and logs AWS infrastructure evidence to Google Sheets on a recurring schedule. Stop manually exporting IAM user lists and CloudTrail logs fo...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps use case.