Clean up n8n sample agent as we can now directly use n8n new node #100
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pdwarf
reviewed
Dec 11, 2025
| - Microsoft Agent 365 SDK | ||
| - n8n instance with webhook endpoint | ||
| - Microsoft Agent 365 | ||
| - n8n instance with Microsoft Agent 365 Node |
There was a problem hiding this comment.
We should specify the min required n8n version here that contains the Microsoft Agent 365 Node
pdwarf
reviewed
Dec 11, 2025
| #### Step 2: Publish to Microsoft Admin Center | ||
|
|
||
| Publish your agent for administrative management: | ||
| - Follow the [publish guide](https://learn.microsoft.com/en-us/microsoft-agent-365/developer/publish-deploy-agent?tabs=dotnet#step-2-publish-to-microsoft-admin-center) |
There was a problem hiding this comment.
Since for n8n, users will just need to generate a valid manifest.zip package, this guide is confusing. I'd suggest to outline the steps here:
- Download the manifest directory from the sample agent
- Edit the manifest.json file (at minimum, give it a custom
idand tweak theagenticUserTemplates.idvalue) - Edit the agenticUserTemplateManifest.json so that it matches the
agenticUserTemplates.idyou set in step 2. - Compress all files inside the manifest directory into a manifest.zip file (make sure you're not compressing the folder, but just the individual files)
- Go to MAC > Agents > All agents > Upload custom agent and upload the zip file.
pdwarf
reviewed
Dec 11, 2025
|
|
||
| Configure authentication credentials: | ||
| - Navigate to your app registration in the Azure Portal | ||
| - Follow the [credentials guide](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials?tabs=client-secret) to add a client secret |
There was a problem hiding this comment.
I wasn't able to find an application in the App registrations view, but instead when I searched the Azure Portal by my blueprint id, I then found the app, and from there was able to go > Client credentials > Add a client secret
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Once the new node in n8n gets deployed, users no longer need a separate agent application for all the integrations. Everything is built into n8n.
Waiting on this PR being merged and published: n8n-io/n8n#22449