Skip to main content

Create & delete AWS RDS databases via email commands with Terraform

Workflow preview

Workflow preview
100%
Create & delete AWS RDS databases via email commands with Terraform preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This automated n8n workflow enables the creation and management of AWS RDS databases through email interactions. Users can send emails with commands such as "Create RDS" or "Delete RDS," including ...

Best for

  • DevOps automation workflows
  • Multimodal AI automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.gmail, n8n-nodes-base.code, n8n-nodes-base.ssh, n8n-nodes-base.googlesheets

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title
Create & delete AWS RDS databases via email commands with Terraform
Workflow name
Create & delete AWS RDS databases via email commands with Terraform

This automated n8n workflow enables the creation and management of AWS RDS databases through email interactions. Users can send emails with commands such as "Create RDS" or "Delete RDS," including details like database engine, instance class, and credentials. The workflow parses the email, uses Terraform to execute the requested action on AWS RDS, updates a Google Sheet with the status, and sends a confirmation email.

Fundamental Aspects

  • Gmail Trigger: Initiates the workflow upon receiving a new email in Gmail.
  • Parse Email Content: Analyzes the email body to extract the command (create or delete) and database details like region, identifier, engine, and credentials.
  • Manage RDS Instance: Executes Terraform commands to create or delete the AWS RDS database instance based on the parsed details.
  • Wait For Data: Pauses the workflow to allow time for the RDS operation to complete and data to become available.
  • Update Google Sheet: Appends or updates the Google Sheet with the database instance details, status, and any relevant IDs.
  • Send Confirmation Email: Formats and sends a response email confirming the action taken, including success/failure details.

Setup Instructions

  • Import the Workflow into n8n: Download the workflow JSON and import it via the n8n interface.
  • Configure API Credentials:
    • Set up Gmail API credentials for email triggering and sending.
    • Configure AWS credentials with RDS management permissions.
    • Set up Google Sheets API credentials with read/write access.
    • Ensure Terraform is integrated or nodes are configured for Terraform execution.
  • Prepare Google Sheet: Create a sheet with columns for database identifier, engine, instance class, status, and other relevant fields.
  • Run the Workflow: Activate the Gmail trigger and test by sending an email with a create or delete command.
  • Verify Responses: Check the Google Sheet for updates and your email for confirmation messages.
  • Adjust Parameters: Fine-tune Terraform variables, email parsing logic, or wait times as needed.

Columns For The Google Sheet:

  1. Database Identifier: Unique identifier for the RDS instance (e.g., var.db_identifier).
  2. Engine: Database engine type (e.g., MySQL, PostgreSQL) (e.g., var.db_engine).
  3. Instance Class: RDS instance class (e.g., var.instance_class) (e.g., db.t3.micro).
  4. Allocated Storage: Storage size in GB (e.g., var.allocated_storage) (e.g., 20).
  5. Region: AWS region for the instance (e.g., var.aws_region) (e.g., us-east-1).
  6. Username: Database admin username (e.g., var.db_username) (e.g., admin).
  7. Password: Database admin password (e.g., var.db_password) (e.g., SecurePassword123).
  8. Status: Current status of the RDS instance (e.g., creating, deleted).
  9. Database Name: Name or tag for the database (e.g., var.db_name) (e.g., MyRDSDatabase).

Technical Dependencies

  • Gmail API: For receiving trigger emails and sending confirmations.
  • AWS RDS API: For database management (via Terraform).
  • Google Sheets API: For logging and updating database status.
  • Terraform: For infrastructure-as-code management of RDS instances.
  • n8n: For workflow automation and node integrations.

Customization Possibilities

  • Support Additional Commands: Extend to include update or snapshot operations for RDS instances.
  • Enhance Parsing: Improve email content analysis with AI for better intent detection.
  • Add Database Engines: Include support for more RDS engines like Oracle or SQL Server.
  • Integrate Monitoring: Add nodes to monitor RDS performance and alert via email.
  • Customize Sheets: Modify sheet columns or add visualizations for database metrics.
  • Security Enhancements: Incorporate additional validation for sensitive credentials in emails.

Want a tailored workflow for your business? Our experts can craft it quickly Contact our team

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 - Workflow Overview

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

Block 2 - Terraform Vars

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

Block 3 - Gmail Trigger

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

Block 4 - Parse Email Content

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

Block 5 - Manage RDS Instance

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

Block 6 - Update Google Sheet

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

Block 7 - Send Confirmation Email

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

Block 8 - Terraform Config

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

3. Summary Table

Workflow Create & delete AWS RDS databases via email commands with Terraform
Complexity intermediate
Nodes 8
Categories DevOps, Multimodal AI
Author Oneclick AI Squad
Published 12 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7294/7294.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 Create & delete AWS RDS databases via email commands with Terraform do?

This automated n8n workflow enables the creation and management of AWS RDS databases through email interactions. Users can send emails with commands such as "Create RDS" or "Delete RDS," including ...

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 DevOps, Multimodal AI use case.