AWS IAM n8n INTEGRATION: AUTOMATE AWS IAM WITH N8N

This action retrieves multiple IAM groups from your AWS account in a single operation. It's essential for auditing purposes, generating reports, or feeding group data into downstream workflow steps that need to process multiple groups at once.

Key parameters:

• Credential to connect with: Select your configured AWS IAM account from the dropdown. Required.
• Return All: Boolean toggle that determines whether to fetch every group in your account. When disabled, respects the Limit parameter. Optional.
• Limit: Numeric field specifying the maximum number of groups to return. Defaults to 100. Optional.
• Include Users: Toggle to include the list of users belonging to each group in the response. Useful when you need membership data alongside group information. Optional.

Use cases: Export all IAM groups and their members to a Google Sheet for compliance documentation, feed group data into a loop that checks each group's policies, create an inventory of all groups before a major access restructuring.

This action permanently removes an IAM group from your AWS account. Use it carefully—deletion is irreversible and the group must be empty (no users attached) before AWS allows deletion.

Key parameters:

• Credential to connect with: Select your AWS IAM credentials from available options. Required.
• Group: Text field where you enter the exact name of the IAM group to delete. Supports expressions for dynamic values from previous nodes. Required.

Use cases: Clean up deprecated project groups after a project concludes, remove temporary groups created for time-limited access scenarios, automate group removal as part of a decommissioning workflow.

This action modifies an existing IAM group's configuration. In AWS IAM, updating a group primarily means changing its name or path, which this action facilitates without needing to delete and recreate the group.

Key parameters:

• Credential to connect with: Your AWS IAM account credentials. Required.
• Group: Method to identify the group, typically "By Name" from the dropdown. Required.
• Group Name: Text field for the current name of the group you want to update. Required.
• Additional Fields: Expandable section where you can add extra properties like a new group name or path by clicking "Add Option".

Use cases: Rename groups to match updated naming conventions, update group paths to reorganize your IAM structure, batch-rename groups when restructuring department access.

This action retrieves detailed information about a specific IAM group. Unlike "Get many groups," this focuses on a single group and can optionally include the list of users who belong to it.

Key parameters:

• Credential to connect with: Your AWS IAM account from the dropdown. Required.
• Group: Select how to identify the group (typically "By Name"). Required.
• Include Users: Boolean toggle to include user membership data in the response. Optional.

Use cases: Verify a group exists before attempting to add users to it, fetch group membership for validation in onboarding workflows, retrieve group details to display in a Slack notification or dashboard.

This action creates a new IAM group in your AWS account. Groups are fundamental to organizing users and applying policies collectively rather than individually.

Key parameters:

• Credential to connect with: AWS IAM credentials for authentication. Required.
• Group Name: Text input specifying the name for your new group. Must be unique within the AWS account. Required.
• Additional Fields: Optional section for adding properties like a path to organize the group within your IAM hierarchy.

Use cases: Automatically create a group for each new project or team, set up groups based on role definitions from your HR system, create temporary access groups for contractors or external collaborators.

This action removes an IAM user from a specified group, effectively revoking any permissions that user inherited from group membership. The user account itself remains intact.

Key parameters:

• Credential to connect with: Select your AWS IAM credentials. Required.
• User: Specify the user to remove, typically "By Name" with the user name provided. Required.
• Group: Specify the group from which to remove the user, also typically "By Name". Required.

Use cases: Remove departing employees from all their groups during offboarding, revoke project access when someone moves to a different team, implement time-based access by removing users from groups after a period.

This action modifies an existing IAM user's configuration. You can update attributes like the user's name or path without deleting and recreating the account.

Key parameters:

• Credential to connect with: Your AWS IAM credentials. Required.
• User: How to identify the user, typically "By Name". Required.
• User Name: Text field for the current name of the user you're updating. Required.
• Result: Optional field to store the operation's output for use in subsequent nodes.

Use cases: Update usernames when employees change their names, reorganize users by modifying their paths, batch-update user attributes based on HR system changes.

This action retrieves detailed information about a specific IAM user, including their creation date, path, user ID, and ARN. Essential for verification and audit workflows.

Key parameters:

• Credential to connect with: AWS IAM credentials from your configured accounts. Required.
• Resource: Fixed to "User" for this action.
• Operation: Fixed to "Get".
• User: Select identification method (typically "By Name") and provide the username. Required.

Use cases: Verify a user exists before performing operations on their account, retrieve user ARN for use in policy configurations, audit individual user details as part of a compliance check.

This action retrieves multiple IAM users from your AWS account, making it ideal for bulk operations, reporting, and auditing scenarios where you need to process many users at once.

Key parameters:

• Credential to connect with: Select your AWS IAM account. Required.
• Return All: Boolean toggle to fetch all users regardless of the limit. When enabled, pagination is handled automatically.
• Limit: Numeric value specifying maximum users to return when Return All is disabled. Defaults to 100. Required.
• Additional Fields: Expandable section for adding filters or options via "Add Field".

Use cases: Generate a complete user inventory for security audits, export all IAM users to a database for external reporting, feed user data into workflows that check for inactive accounts.

This action assigns an existing IAM user to a specified group. The user immediately inherits all policies attached to that group, making this crucial for access provisioning.

Key parameters:

• Credential to connect with: Your AWS IAM account credentials. Required.
• User: Select an IAM user from the dropdown or provide the name. Required.
• Group: Select the target group from available groups or provide the name. Required.

Use cases: Automatically add new employees to their department's group upon onboarding, grant project access by adding users to project-specific groups, implement role-based access control by adding users to role groups.

This action creates a new IAM user in your AWS account. It's the foundation for automated user provisioning workflows and eliminates manual user creation through the AWS console.

Key parameters:

• Credential to connect with: AWS IAM credentials for authentication. Required.
• User Name: Text input for the new user's name. Must be unique within your AWS account. Supports expressions for dynamic naming based on input data. Required.
• Result: Informational output showing what the created user looks like.

Use cases: Automatically create IAM users when new employees are added to your HR system, provision service accounts for new applications or microservices, create users as part of a larger onboarding workflow that also assigns groups and policies.

This action permanently removes an IAM user from your AWS account. The user must have no active access keys, MFA devices, or group memberships before deletion—or you'll need to remove those first.

Key parameters:

• Credential to connect with: AWS IAM credentials from your configured list. Required.
• User: Specify identification method (typically "By Name") and provide the username of the account to delete. Supports expressions for dynamic values. Required.

Use cases: Remove user accounts during offboarding when employees leave, clean up service accounts that are no longer needed, automate deletion of temporary users after their access period expires.