Skip to content

Conversation

shad03152015
Copy link

Summary

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

@CLAassistant
Copy link

CLAassistant commented Oct 20, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Compyle Bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@n8n-assistant n8n-assistant bot added community Authored by a community member core Enhancement outside /nodes-base and /editor-ui node/new Creation of an entirely new node in linear Issue or PR has been created in Linear for internal review labels Oct 20, 2025
@n8n-assistant
Copy link

n8n-assistant bot commented Oct 20, 2025

Hey @shad03152015,

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email nodes@n8n.io and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-5123". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.

@shad03152015 shad03152015 force-pushed the compyle/cmgyzio2e00v3qyi267tuqvg3-4c6d4b9 branch from 0e3ebca to 15a7c0f Compare October 21, 2025 05:30
@@ -0,0 +1 @@
import type{INodeType,INodeTypeDescription}from'n8n-workflow';import{resourceOperations,resourceFields}from'./descriptions';import{BASE_URL}from'./helpers/constants';export class AwsAugmentedAI implements INodeType{description:INodeTypeDescription={displayName:'AWS AugmentedAI',name:'awsAugmentedAI',icon:'file:augmentedai.svg',group:['transform'],version:1,subtitle:'={{["operation"]+": "+["resource"]}}',description:'Interact with AWS AugmentedAI',defaults:{name:'AWS AugmentedAI'},inputs:['main'],outputs:['main'],credentials:[{name:'aws',required:true}],requestDefaults:{baseURL:BASE_URL,headers:{'Content-Type':'application/json'}},properties:[{displayName:'Resource',name:'resource',type:'options',noDataExpression:true,options:[{name:'Resource',value:'resource'}],default:'resource'},...resourceOperations,...resourceFields]};}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: AWS Node Subtitles Lack Parameter Accessors

The subtitle expression in many AWS nodes is missing the $parameter accessor. This causes the node subtitle to display literal strings like 'operation' and 'resource' instead of the actual selected values, leading to incorrect UI display.

Additional Locations (4)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Authored by a community member core Enhancement outside /nodes-base and /editor-ui in linear Issue or PR has been created in Linear for internal review node/new Creation of an entirely new node

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants