Problem with workflow publish/unpublished. Can't Enable MCP. Disabled nodes - ERRORS

Questions
1

{
“nodes”: [
{
“parameters”: {
“updates”: [
“com.twilio.messaging.inbound-message.received”,
“com.twilio.voice.insights.call-summary.complete”
]
},
“id”: “266791f8-fd1a-49e7-a715-794b058b2941”,
“name”: “SMS/Phone Trigger2”,
“type”: “n8n-nodes-base.twilioTrigger”,
“typeVersion”: 1,
“position”: [
-110624,
31520
],
“webhookId”: “68a086b3-248e-4f83-881f-e40f93d9d709”,
“credentials”: {
“twilioApi”: {
“id”: “9AFffJtlnPRhc3zX”,
“name”: “Twilio account 2”
}
}
}
],
“connections”: {
“SMS/Phone Trigger2”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “b526f2ee2c55afbed032cd81d3464aa105282be6c729246f978534fa6d63883c”
}
}

2

MCP only works with Webhook, Schedule, Form, or Chat triggers so your Twilio Trigger won’t be eligible for it, you’d need to swap it out for a Webhook trigger and have Twilio point to that instead. Also that disabled AI Agent node is probably what’s causing your publish errors, try deleting it entirely rather than just disabling it.

3

MCP only works with Schedule, Webhook, Form, or Chat triggers so your Twilio Trigger won’t qualify for it regardless. For the publish issue, delete the disabled nodes entirely instead of leaving them disabled, n8n v2 won’t let you republish with disabled triggers sitting in the workflow.

4

Based on the workflow data you’ve shared @rdnetech here are the issues preventing you from publishing and enabling MCP:

  1. Disabled nodes with errors:

    • The “Leasing Operations Agent2” node is disabled ("disabled": true)

    • It has "onError": "continueRegularOutput" set, which suggests it was experiencing errors

    • The node is disconnected - it has no outgoing connections

  2. Incomplete workflow:

    • The SMS/Phone Trigger2 has no connections to any other nodes

    • The Leasing Operations Agent2 is isolated with no connections

    • These nodes aren’t linked together to form a functional workflow

Let me know if you need a fix for this.

5

Hi @rdnetech
looks like your agent node is completely toggled off in that snippet. it has the disabled flag set to true.

when a core node is disabled like that, n8n usually blocks you from publishing the workflow. it also stops you from fully configuring things like MCP since the node is technically bypassed. just select the agent node on your canvas and hit ‘d’ on your keyboard to turn it back on.

also i only see the agent node in the json — from what i’ve seen you absolutely need an active trigger node connected before the system lets you publish anyway. lmk if it still throws errors after enabling it.

6

This is the thing…we can’t toggle it back on. We can’t publish. Should we just create a new workflow and I’mport the json there? i.e., would just creating a new workflow and copying the existing configuration to it be more simple? I think the problem is we had 3 workflows on the same canvas. They were iterations of the original. The old workflows are now deleted leaving the remaining, newest version on the canvas.