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
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.
Hey @mfranma Jonathan here from the product team. We’re just starting to look at adding some related functionality this quarter to provide better controls on which node and credential types can be used on an instance. One thing we have been considering is how granular we go in terms of controls and specific ‘operational’ controls at the node level is something we’re considering (although probably wouldn’t be in the first few iterations. The main focus will be on bringing to the UI an admin interface to allow/restrict different node and credentials types at the instance or project level.
Happy to share more on that if interested. But the one question I did have for you was a bit more context on why you specifically need to limit this action inside the service now node. Could you share an example of where this has been a problem for you in the past when users build workflows? Do you have any other nodes where this would apply too?
will look into those options