Duplicating workflow with Trello/Webhook trigger retains ghost credential IDs and causes SQLITE_CONSTRAINT error

Questions
1

Describe the problem/error/question

When duplicating an existing workflow that contains a Trello Trigger node, n8n retains the original workflow’s hidden webhook and credential references in the database.
Even after changing the credentials and updating the Trello node parameters in the duplicated workflow, n8n keeps throwing a credential error pointing to the deleted original credential ID:

What is the error message (if any)?

SQLITE_CONSTRAINT error

Share the output returned by the last node

No output - just error pop-ups

Information on your n8n setup

  • n8n version: 2.327
2

Hey @Wes_Koster, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@kjooleng, @achamm, @Abdulsalam_Alturk - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

The root cause is that duplicating a workflow copies the Trello Trigger node’s webhookId as-is, so the new workflow’s node still references the old webhook/credential row in the database, causing the SQLITE_CONSTRAINT conflict when n8n tries to register it. Changing the credential in the UI doesn’t regenerate that hidden webhookId. Fix: delete the Trello Trigger node in the duplicated workflow entirely and drag in a fresh Trello Trigger node (this generates a new unique webhookId), then reattach your working credential and re-save/activate. Verify by checking the workflow activates without errors and the new webhook URL differs from the original.

5

Hey @Wes_Koster and thank you for your report.

Could you share some more details.

  • How did you duplicate the workflow? Using the “Duplicate” button from the workflow menu?
  • When exactly is the error shown? When you try to save the Workflow? When you try to publish it?
  • Could you share the stack trace of that error
6

How did you duplicate the workflow? Using the “Duplicate” button from the workflow menu?

Yes, I duplicated the original, fully working workflow using the “Duplicate” option directly from the workflow menu (the three dots ... next to the workflow in the list).

When exactly is the error shown? When you try to save the Workflow? When you try to publish it?

  • Credential Error: Appears when trying to Save or Publish (toggle to Active) the duplicated workflow, even after deleting the old Trello node, creating a new Trello Trigger node, and mapping it to a newly created Trello credential. The error keeps pointing to the old (deleted) credential ID: Unexpected: Credential with ID "............" does not exist for type "trelloApi".

  • SQLITE_CONSTRAINT Error: Appears when trying to Delete the duplicated workflow from the menu after this issue occurs. The workflow gets locked in the database and cannot be deleted.

Could you share the stack trace of that error?

Since I am on n8n Cloud, I don’t have direct access to server backend logs. However, the pop-up errors in the UI display:

  1. Workflow could not be activated - Unexpected: Credential with ID ".........." does not exist for type "trelloApi".

  2. Problem deleting workflow - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed

8

Thanks for explaining the root cause behind the webhookId retention!

However, in my case, deleting the Trello Trigger node and replacing it with a fresh one did not solve the issue.

I tried deleting the trigger node, adding a brand new Trello Trigger node, and attaching the new credential multiple times. Despite this, saving or activating still threw the same Unexpected: Credential with ID "............" does not exist error for the deleted credential.

Once the workflow entered this state, deleting the nodes completely and leaving a totally empty canvas still produced the SQLITE_CONSTRAINT: FOREIGN KEY constraint failed error when trying to delete the workflow itself.

The only workaround that worked for me was leaving the broken duplicated workflow behind and recreating the entire workflow manually from scratch on a completely new canvas.

9

Thank you for the additional details @Wes_Koster !

Since you are on n8n cloud, could you share your account name “.app.n8n.cloud” and the ID/name of the workflow you can’t delete? Either in this thread or you can DM me.

10

Hi @tomi, because my account is brand new, the forum isn’t allowing me to click the “Message” button to send a DM. Could you please send me a quick private message first? I will reply to it with my instance name right away!