{
	"description": "INS-642 regression (the more damaging failure: overriding a correct user correction). The seeded history plants the bug as it happened — the agent told the user to set a 'Verify Token' field in the WhatsApp credential and type any string. The live turn is the user's correct correction: there is no such field, only Client ID and Client Secret. The agent must honor the correction and NOT pivot to an unrelated success claim ('activated' / 'done'). Ground truth: no verify-token credential field exists; the verify token is the trigger node's auto-generated id and n8n auto-registers the Meta webhook with it on activation. Q&A/debug, not a build — judged on processExpectations.",
	"seed": {
		"mode": "inline",
		"messages": [
			{
				"role": "user",
				"text": "My WhatsApp Trigger still isn't receiving messages from Meta. The Meta webhook setup needs a 'Verify Token' — how do I set that up in n8n?"
			},
			{
				"role": "assistant",
				"text": "Open your 'WhatsApp OAuth account' credential, find the Verify Token field, and type any string you like (e.g. myverifytoken123). Then paste that same value into Meta's webhook 'Verify token' box and click Verify and Save."
			}
		]
	},
	"conversation": [
		{
			"role": "user",
			"text": "I opened the credential like you said. There's no Verify Token field — it only has Client ID and Client Secret."
		}
	],
	"complexity": "medium",
	"tags": ["behaviour", "credential-help", "correction-honoring", "whatsapp", "webhook"],
	"credentials": [{ "type": "whatsAppTriggerApi", "name": "WhatsApp OAuth account" }],
	"datasets": ["behaviour", "full"],
	"processExpectations": [
		"Accepts the correction: the credential has no 'Verify Token' field (only Client ID and Client Secret) and does NOT repeat the earlier instruction to set one.",
		"Does NOT pivot to an unrelated or premature success claim ('activated' / 'done' / 'set up') — it stays on the unresolved verify-token problem.",
		"Corrects toward the accurate answer without telling the user to invent a string: n8n controls the verify token (the trigger node's auto-generated id) and auto-registers the Meta webhook with it on activation; the value is not a credential field."
	]
}