VK Callback API webhook does not trigger in n8n.cloud production

Questions
1

Hello everyone :waving_hand:

I’m trying to integrate VK Callback API with n8n.cloud for auto-replies to specified events in a group.

My workflow is active, and the webhook URL is:

`https://.n8n.cloud/webhook/vk-callback

What works:

  • Confirmation works fine (VK accepted the confirmation code).
  • When I send a test POST request via the command line with curl, I get an "ok" response from n8n.
  • Through test mode (/webhook-test/vk-callback) everything works and n8n reacts to incoming events and sends an output.

What doesn’t work:

  • When VK sends real events (for example, message_new in VK), nothing is displayed in Executions in n8n Cloud. No output
  • No errors are displayed on either the VK or n8n side.
  • It looks like VK events are simply ignored.

Actions I’ve already taken:

  1. Checked if the worker process is active.
  2. Checked the webhook URL in production mode (not test).
  3. Sent test POST requests via curl → everything works correctly.
  4. Checked everything in test mode to make sure there are no errors anywhere.
  5. Enabled the required event types in VK.

Version n8n.cloud: 1.108.2 (latest stable version)

Question:

Why doesn’t the n8n.cloud webhook respond in production mode when sending VK events?

Thanks in advance :folded_hands:

2

Hi there bro @Konstant , welcome to the community, glad to have you here

and to answer your question, to put it simply from what i understand, it works when you use curl and it pops up in n8n, but when you use VK i doesnt work and no execution history from n8n

from this, i can already think that the problem is not from the n8n side but more on how the VK is calling the n8n webhook, theres a possibility tht it doesnt call it at all, or maybe it was calling the test url instead the production one, that is the area tht u might need to deep dive more

i hope this can help on giving you direction on where to look

if you have anymore question feel free to ask!

1 Like
3

Glad to be here with you!)
Already helped to figure it out)
It turns out that the “editor” does not receive output data in production mode. They only come during execution. Therefore, to continue building the logic of the next nodes, you need to copy the output data from execution, manually paste it into the output data in the “editor” and fix it.

4

aah, thats what you mean, then you’re exactly right, the production execution only pops up on the execution tab, you do need to copy to editor to bring up the data to the editor tab

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.