MCP

Parameter Drift in n8n Workflows Allows Approved Action A to Trigger Unrelated Action B in Bitrix24

An engineer tested an n8n orchestration workflow integrating Groq AI agents with Bitrix24 via MCP and discovered that human approval of one action did not technically bind to the parameters executed downstream. The experiment used a controlled update of a synthetic task title, where the approval screen and execution node received parameters from independent sources, creating a parameter drift scenario. Although Bitrix24 rejected the mismatched call and no unauthorized change occurred, the architecture allowed an approved action A to reach an execution attempt for action B. The fix introduced a single Action Envelope object carrying target system, task ID, operation, expected baseline, and requested change values, combined with a fresh pre-write read and post-write verification. This ensured that the same parameters flowed from approval through execution and final state confirmation. The case highlights that a simple approved=true flag is insufficient for state-changing AI agent workflows without explicit data binding and evidence reconstruction at each boundary.