Do webhook triggers block other triggers?

Hi. I’m new to n8n but am already super impressed. I’ve been pleasantly surprised how easy it has been to work with. I’ve now run into my first issue and I’m wondering whether what I’m trying to do is simply not possible, or whether I’m doing something wrong.

Basically, I am looking to create a workflow where:

  1. Check for new files in a specific folder on Google Drive
  2. Send those files off for processing elsewhere (POST request)
  3. Once those files have been processed, upload them to a specific folder on Google Drive

The processing of the files after they’ve been sent with the POST request can take a while. I’ve successfully tested the full workflow with polling by checking if the processing has completed.

However, when sending the files for further processing elsewhere, it is possible to provide a callback URL instead of using polling. To try and do this, I’ve also created a webhook trigger in the same workflow and send the provided URL when sending the file off for processing.

This does not appear to work. It seems like the webhook trigger “cancels out” the Google Drive trigger, as it never fires when clicking “Test workflow.” But as soon as I deactivate the webhook trigger, the Google Drive trigger works again.

Is what I am trying to do not possible? Or is there a way to have both triggers work? I’ve tried searching for this but the only thing I’ve found was confirmation that there can be multiple webhook triggers in a workflow, but I didn’t find anything about it being possible to have a webhook trigger and a trigger of another kind.

Thanks in advance.

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @Cal

Welcome to the community :birthday:

The quick version for this is when pressing the test button we only listen for one node most of the time this will change in the future and you will be able to pick the node.

For now though to use both at once the quickest option would be to enable the workflow logging under the workflow settings then activate the workflow and it should start working but each trigger is considered its own workflow run do you will see some logs where the google trigger runs and others where the webhook runs.

One thing you could do is add a wait node to the top part and tell it to wait for a webhook and use the url for that by doing this you won’t need the other webhook node and everything is inline.

Hopefully this helps.

1 Like

Hi Jon :wave: That makes sense and you’re absolutely right - just enabling the workflow, everything works as expected! I will give the wait for a webhook a try as well. Thanks so much!

1 Like

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