Managed to get n8n nodes to communicate input data to SCM and return that data.
I am also cleaning up SCM API while doing this.
All changes in the SCM API are reflected in the postman collection
All previous API routes are still supported, however only the newest routes are being displayed on postman.
Eg, all project routes renamed to task
Refactoring the task find inside n8n.
In addition to coding the n8n node, I am also simplifying and redoing API calls where required.
For task name searching, instead of requiring an exact case match to return the task, instead now you can input a partial name.
Do a partial name search for ‘google’
FYI: Task name is jobName in the database.
Just tasks with Google in the name.
Great stuff, I already have 3 feature request in my mind after this is done 
I use deepwiki to understand any library/framework on github.
Nice let me see.
Have to admit the dev docs for n8n are poor. Couldn’t even find a page that doc all methods and props on objects.
The only way I’ve been able to code anything was opening existing nodes and looking at their source.
Makes progress slow.
Their setup page is OK, but beyond the example project there is no help.
Most the docs are user docs for how to use node.
