See llms.txt for all machine-readable content.

AWS IAM and Myphoner integration

Save yourself the work of writing custom integrations for AWS IAM and Myphoner 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 IAM and Myphoner

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 IAM and Myphoner integration: Create a new workflow and add the first step

Monitor & alert on inactive AWS IAM users with Slack notifications

AWS IAM Inactive User Automation Alert Workflow > Weekly job that finds IAM users with no activity for > 90 days and notifies a Slack channel. > ⚠️ Important: AWS SigV4 for IAM must be scoped to us-east-1. Create the AWS credential in n8n with region us-east-1 (even if your other services run elsewhere). Who’s it for SRE/DevOps teams that want automated IAM hygiene checks. Security/compliance owners who need regular inactivity reports. MSPs managing multiple AWS accounts who need lightweight alerting. How it works / What it does Weekly scheduler – kicks off the workflow (e.g., every Monday 09:00). Get many users – lists IAM users. Get user – enriches each user with details (password status, MFA, etc.). Filter bad data – drops service-linked users or items without usable dates. IAM user inactive for more than 90 days? – keeps users whose last activity is older than 90 days. Last activity is derived from any of: PasswordLastUsed (console sign-in) AccessKeyLastUsed.LastUsedDate (from GetAccessKeyLastUsed if you add it) Fallback to CreateDate if no usage data exists (optional) Send a message (Slack) – posts an alert for each inactive user. No operation – path for users that don’t match (do nothing). How to set up Credentials AWS (Predefined → AWS) Service: iam Region: us-east-1 ← required for IAM Access/Secret (or Assume Role) with read-only IAM perms (see below). Slack OAuth (bot in your target channel). Requirements n8n (current version). AWS IAM permissions (minimum): iam:ListUsers, iam:GetUser (Optional for higher fidelity) iam:ListAccessKeys, iam:GetAccessKeyLastUsed Slack bot with permission to post in the target channel. Network egress to iam.amazonaws.com. How to customize the workflow Change window: set 60/120/180 days by adjusting minus(N, 'days'). Audit log: append results to Google Sheets/DB with UserName, Arn, LastActivity, CheckedAt. Escalation: if a user remains inactive for another cycle, mention @security or open a ticket. Auto-remediation (advanced): on a separate approval path, disable access keys or detach policies. Multi-account / multi-region: iterate a list of AWS credentials (one per account; IAM stays us-east-1). Exclude list: add a static list or tag-based filter to skip known service users. Notes & gotchas Many users never sign in; if you don’t pull GetAccessKeyLastUsed, they may look “inactive”. Add that call for accuracy. PasswordLastUsed is null if console login never happened. IAM returns timestamps in ISO or epoch—use toDate/toDateTime before comparisons.

Build your own AWS IAM and Myphoner integration

Create custom AWS IAM and Myphoner 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 IAM supported actions

Supported methods for Myphoner

Delete
Get
Head
Options
Patch
Post
Put

To set up Myphoner integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Myphoner to query the data you need using the API endpoint URLs you provide.

See the example here

Requires additional credentials set up

Use n8n's HTTP Request node with a predefined or generic credential type to make custom API calls.

AWS IAM and Myphoner integration details

AWS IAM

AWS IAM

AWS Identity and Access Management (IAM) enables secure control of access to AWS services and resources. It allows you to manage users, groups, and permissions, ensuring that only authorized individuals can perform specific tasks. IAM provides flexible, granular security controls to safeguard your AWS environment effectively.

Myphoner

Myphoner

Myphoner is a sales CRM platform that helps businesses manage and streamline their outbound sales campaigns. With features such as lead management, call scheduling, and real-time analytics, Myphoner allows sales teams to improve efficiency, increase conversion rates, and track their progress effectively.

Supercharge your CRM

Need a more powerful integration with your CRM? n8n lets you go beyond standard integrations offered by popular CRMs!

Learn more

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 IAM integrations

Looking to integrate Slack and VirusTotal in your company?

Three colleagues talking around laptops at a shared desk

Trusted by teams building smarter workflows.

Why

Why use n8n to integrate AWS IAM with Myphoner

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

Man in a brown jacket working at his desk by a window