If a n8n credential exists for the node, the credential cannot be cleared if using different servers on individual nodes within workflows.
Workarounds
Delete all n8n NTFY API credentials so that the credential dropdown within individual nodes is blank
Create a separate token for each server (even though by default ntfy.sh does not require credentials)
Create a blank credential by using a space character as the token within the credential
Ultimate solution
Find a way for the default credentials for each individual node to be blank
Although through my current research, there isn't a way to do this in n8n currently. The unfortunate solution may be turning the credential into a string field with password type option. I refrained from doing this in the first place so that tokens are not accidentally shared through the workflow json if downloaded.
Issue Description
If a n8n credential exists for the node, the credential cannot be cleared if using different servers on individual nodes within workflows.
Workarounds
NTFY APIcredentials so that the credential dropdown within individual nodes is blankspacecharacter as the token within the credentialUltimate solution
Find a way for the default credentials for each individual node to be blank
Although through my current research, there isn't a way to do this in n8n currently. The unfortunate solution may be turning the credential into a string field with password type option. I refrained from doing this in the first place so that tokens are not accidentally shared through the workflow json if downloaded.