n8n/packages/@n8n/instance-ai/evaluations/data/workflows/mocks-node-with-two-credentials.json

28 lines
1.6 KiB
JSON

{
"description": "#2b: Sibling of mocks-node-with-one-credential. With two matching credentials available no auto-attach is possible, so the builder must mock the node during verification. Together the pair covers both credential-count paths with the same expectation: verification never calls the real service.",
"conversation": [
{
"role": "user",
"text": "Every morning at 9am, post the message \"Daily build completed\" to the Slack channel #updates."
}
],
"complexity": "simple",
"tags": ["behaviour", "credentials", "mocking", "slack", "verification"],
"credentials": [{ "type": "slackApi" }, { "type": "slackApi" }],
"triggerType": "schedule",
"datasets": ["behaviour", "full"],
"processExpectations": [
"Two Slack credentials were offered to the agent during the build — both appeared in the agent's available-credentials list — confirming the ambiguous-credential precondition.",
"The agent ran a verification of the built workflow (a verification execution was attempted, not skipped).",
"The build's verification run succeeded — the Slack post did not fail with a credential or authentication error — consistent with the builder exercising the node against mocked data rather than the live Slack API."
],
"executionScenarios": [
{
"name": "happy-path",
"description": "The scheduled run posts the message to Slack",
"dataSetup": "The Slack chat.postMessage call returns { \"ok\": true, \"ts\": \"1700000000.000100\", \"channel\": \"C0UPDATES\" }.",
"successCriteria": "The workflow executes without errors and posts the message \"Daily build completed\" to Slack #updates. A schedule trigger is present."
}
]
}