I've made a "small" extension for iTOP - use external WF engine instead of "object copier"..
Main functions in iTOP:
-WorkOrderTemplate: You can define templates for specific WorkOrder type. Team_id, resolution_time for OLA (based on service SLA), description
-Extended ServiceSubcategory: you can map servicesubscription to an external WF (the list come from n8n via iTOP RESTApi)
-The n8n and the iTOP communicate via RestAPI (startWF,create- update task, apply stimulus and so on)
-You can see the impacted tasks in UserREQ/Incident
In n8n:
-you can define parallel and dependended tasks, (of course you can monitor the status)
-when you're designing a new WF, you can choose from the actual WorkOrderTemplates (via RestApi from iTOP)
-after you activate the new WF, n8n insert the new record to iTOP (WFAvail... tabl), so you can select it in ServiceSubcategory...
Architecture:
- All in "one" packaged container :
- itop-docker:
- - - - - db
- - - - - www
- - -- - -n8n
with shared network
Next steps:
- Data Separation/Segmentation for confidental data ( eg. HR Onboarding process) (REQ/INC/TASK)
- Implement Custom Fields to Tasks
- Field/data interaction between parent/child tasks....
- change n8n database to PG & update the container definition
Hello,
I've made a "small" extension for iTOP - use external WF engine instead of "object copier"..
Main functions in iTOP:
-WorkOrderTemplate: You can define templates for specific WorkOrder type. Team_id, resolution_time for OLA (based on service SLA), description
-Extended ServiceSubcategory: you can map servicesubscription to an external WF (the list come from n8n via iTOP RESTApi)
-The n8n and the iTOP communicate via RestAPI (startWF,create- update task, apply stimulus and so on)
-You can see the impacted tasks in UserREQ/Incident
In n8n:
-you can define parallel and dependended tasks, (of course you can monitor the status)
-when you're designing a new WF, you can choose from the actual WorkOrderTemplates (via RestApi from iTOP)
-after you activate the new WF, n8n insert the new record to iTOP (WFAvail... tabl), so you can select it in ServiceSubcategory...
Architecture:
- All in "one" packaged container :
- itop-docker:
- - - - - db
- - - - - www
- - -- - -n8n
with shared network
Next steps:
- Data Separation/Segmentation for confidental data ( eg. HR Onboarding process) (REQ/INC/TASK)
- Implement Custom Fields to Tasks
- Field/data interaction between parent/child tasks....
- change n8n database to PG & update the container definition
Last edit: Peter, U 2025-10-10