AWS COGNITO n8n INTEGRATION: AUTOMATE AWS COGNITO WITH N8N

The "Get many users" action is your go-to for retrieving user lists from any Cognito user pool. Whether you need to export all users for analysis, sync them to another system like Google Sheets, or simply audit who has access to your application, this action handles it efficiently.

Key parameters:

• Credential to connect with: Select your configured AWS IAM account from the dropdown. This is required for authentication.
• User Pool: Choose your target user pool by ID. This is required—you must specify which pool to query.
• Return All: Toggle this on to retrieve every user in the pool, or leave it off to use pagination. Optional but useful for large pools.
• Limit: When Return All is off, this numeric field (default: 50) controls how many users to fetch per request. Optional.
• Simplify: Enable this toggle to receive cleaner, more streamlined user data—stripping out metadata you don't need. Optional.
• Filters: Add specific filter conditions to narrow results. Filter by email, status, or custom attributes. Optional but powerful for targeted queries.

Common use cases: Export all users to a Google Sheet for stakeholder review. Sync active users to your email marketing platform nightly. Identify users matching specific attribute patterns for targeted communications.

The "Update user" action lets you modify any attribute on an existing Cognito user. This is essential for keeping user profiles synchronized with your business systems and updating metadata as users progress through your application.

Key parameters:

• Credential to connect with: Your AWS IAM account selection. Required.
• User Pool: Select the user pool by ID containing the user you want to update. Required.
• User: Specify the target user by their ID. Required.
• User Attributes: Click "Add Attribute" to specify which attributes to update. You can modify standard attributes (email, phone_number, name) or custom attributes defined in your pool.

Common use cases: Update user phone numbers when changed in your CRM like Salesforce. Add custom attributes like subscription_tier or last_login_date. Sync user metadata from external systems automatically.

The "Get user pool" action retrieves configuration details about a specific Cognito user pool. This is invaluable for auditing, documentation, and building dynamic workflows that adapt based on pool settings.

Key parameters:

• Credential to connect with: Your AWS IAM credentials. Required.
• User Pool: Select the pool by ID to retrieve its configuration. Required.
• Simplify: Toggle on to receive a cleaner response format. Optional.

Common use cases: Document your user pool configurations automatically. Verify pool settings before performing bulk operations. Build conditional workflows that check pool policies before user creation.

The "Remove user from group" action handles group membership revocation cleanly. Use it when users downgrade subscriptions, leave teams, or need access revoked for any reason.

Key parameters:

• Credential to connect with: AWS IAM account for authentication. Required.
• User Pool: The pool containing both the user and group. Select by ID. Required.
• User: Specify which user to remove by their ID. Required.
• Group: The group name from which the user will be removed. Required.

Common use cases: Automatically remove users from premium groups when subscriptions expire. Revoke team access when employees are marked inactive in HR systems. Clean up group memberships during user offboarding workflows.

The "Add user to group" action assigns users to Cognito groups, enabling role-based access control through your automation workflows. This is fundamental for permission management at scale.

Key parameters:

• Credential to connect with: Your AWS IAM credentials. Required.
• User Pool: Select the user pool by ID. Required.
• User: Specify the user by ID to add to the group. Required.
• Group: The target group name or ID where the user will be added. Required.

Common use cases: Add users to "premium" group when they complete payment. Assign new employees to department-specific groups based on HR data from Monday.com. Grant beta access by adding users to a "beta-testers" group automatically.

The "Create user" action provisions new users directly in your Cognito user pool. This is essential for automated onboarding flows, admin-created accounts, and migration scenarios.

Key parameters:

• Credential to connect with: AWS IAM account selection. Required.
• User Pool: Target pool where the user will be created. Select by ID. Required.
• User Name: The username for the new user. This text field is required and must be unique within the pool.
• Additional attributes: Configure email, phone number, and custom attributes as needed during creation.

Common use cases: Create Cognito users when leads convert in Attio. Provision accounts automatically when employees are added to your HR system. Migrate users from legacy systems with preserved usernames.

The "Get user" action retrieves complete details about a single user, including all standard and custom attributes. Use it to verify user status, fetch profile data, or check group memberships.

Key parameters:

• Credential to connect with: AWS IAM credentials. Required.
• User Pool: The pool containing the target user. Select by ID. Required.
• User: The specific user ID to retrieve. Required.
• Simplify: Toggle to receive cleaner, more focused response data. Optional.

Common use cases: Fetch user details before processing an order to verify eligibility. Check user status in conditional workflow branches. Retrieve custom attributes for personalization logic.

The "Delete user" action permanently removes a user from your Cognito user pool. Use with appropriate caution—this is irreversible and typically reserved for GDPR requests, account cleanup, or offboarding workflows.

Key parameters:

• Credential to connect with: AWS IAM account. Required.
• User Pool: The pool containing the user to delete. Required.
• User: The user ID to permanently remove. Required.

Common use cases: Process GDPR deletion requests automatically. Remove test accounts after staging environment cleanup. Complete user offboarding by removing Cognito access.

The "Get group" action retrieves information about a specific group within your user pool, optionally including the list of users who belong to it.

Key parameters:

• Credential to connect with: AWS IAM credentials. Required.
• User Pool: Select by ID. Required.
• Group: Specify the group by name. Required.
• Include Users: Toggle on to retrieve the list of users belonging to this group. Optional but useful for membership audits.

Common use cases: Audit who has admin access by fetching the admin group. Verify group exists before adding users to it. Generate group membership reports for compliance.

The "Get many groups" action retrieves multiple groups from a user pool at once, perfect for auditing, documentation, and building dynamic group selection interfaces.

Key parameters:

• Credential to connect with: AWS IAM account. Required.
• User Pool: Select by ID. Required.
• Return All: Toggle on to retrieve all groups, or use Limit for pagination. Optional.
• Limit: Maximum groups to return per request (default: 50). Optional.
• Include Users: Toggle to include user lists for each group. Optional.

Common use cases: Export all groups and their memberships for security audits. Build dynamic dropdown menus populated with available groups. Document group structure across multiple user pools.

The "Delete group" action removes a group from your user pool. Users in the group aren't deleted—they simply lose membership in that group.

Key parameters:

• Credential to connect with: AWS IAM credentials. Required.
• User Pool: The pool containing the group. Required.
• Group: The group name to delete. Required.

Common use cases: Clean up deprecated access tiers after migration. Remove temporary project groups after completion. Automate group lifecycle management.

The "Create group" action provisions new groups in your user pool, establishing the containers for role-based access control.

Key parameters:

• Credential to connect with: AWS IAM account. Required.
• User Pool: Target pool for the new group. Required.
• Group Name: The name for your new group (e.g., "premium-users", "beta-testers"). Required.
• Additional Fields: Optional properties like description or precedence can be added here.

Common use cases: Create subscription tier groups when new pricing plans launch. Provision project-specific groups dynamically. Set up department groups when organizational structure changes.

The "Update group" action modifies existing group properties, such as description or IAM role association.

Key parameters:

• Credential to connect with: AWS IAM credentials. Required.
• User Pool: Select by ID. Required.
• Group: Specify the group by name or ID. Required.
• Additional Fields: Add key-value pairs for properties you want to update. Optional.

Common use cases: Update group descriptions for documentation purposes. Modify IAM role associations when access requirements change. Batch update group metadata across multiple pools.