Block access to specific node action

Describe the problem/error/question

I understand that its possible to block access to nodes as stated in this doc Block access to nodes | n8n Docs
However I would like to block just the action “Create incident” inside the ServiceNow node. As anyone done something similar? Is it possible? Because I can only find the Servicenow node name not the name for the create incident action - needed to block it

Information on your n8n setup

  • n8n version: 2.17.5
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

welcome to the n8n community @mfranma
I’m not sure if blocking access to a node works at the operation/action level inside a node, it seems to only work at the node level. There’s no native way to do exactly what you’re asking for.

From my point of view, your options would be to block the entire ServiceNow node, separate the credential scopes, or fork the ServiceNow node and remove the “Create” operation from it. The last one is more work, but gives you full control.

Thank you for the prompt response :slight_smile: will look into those options

hope it works out :crossed_fingers:

@mfranma,我是產品團隊的 Jonathan。我們剛開始考慮在本季度新增一些相關功能,以便在執行個體上更好地控制可以使用哪些節點和認證類型。我們一直在考慮的一件事是我們在控制方面的細緻程度,節點層級的特定「操作」控制是我們正在考慮的內容(不過可能不會在前幾個版本中推出)。主要重點將放在為 UI 帶來一個管理員介面,以便在執行個體或專案層級允許/限制不同的節點和認證類型。

如果您有興趣,很樂意分享更多相關資訊。但我確實有一個問題想問您,就是想了解更多背景資訊,為什麼您特別需要在服務現在節點內限制此操作。您能否分享一個過去使用者在建立工作流程時遇到此問題的例子?還有其他節點適用於此嗎?