Reconciliate Webhook data + daily trigger feasibility

Questions
1

I have a use case in mind and would like to pick the community mind to understand if it’s feasible or no

I’m receiving data from a webhook, let’s assume that I’m receiving different items during the day.

I want to have a wait node after the webhook that trigger the run at specific time in the day (for instance 7pm), but it should reconciliate all the data that I received separately during the day

FYI - This is for email notificatons I want to group all the data and send one email per day instead of spamming item by item

  • **n8n version: latest
  • **Running n8n via cloud

Thanks Community!

2

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:
3

You can easily achieve this by storing your webhook’s received data into a database (like AirTable), then having a separate workflow that runs on Schedule node at 7pm that calls all entries from AirTable and sends to a Gmail node, for example.

4

Thank you @KHarv, I thought about storing it in Postgres and making that way but that will require 2 workflows, that’s why I’m exploring if this is feasbile through one workflow and with leveraging n8n storage

5

I believe you can have both the Schedule trigger and Webhook trigger in the same workflow file, but since they each lead to different flows it’s no different to having them in separate workflow files.
n8n does not store anything–you can only access data from nodes upstream in the flow.
There is a workaround if you use the community node @telepilotco/n8n-nodes-kv-storage, which is a local key value store. However, if you restart n8n server for any reason, you will lose all your data, so I don’t recommend doing it that way beyond testing.

6

Thank you Jay that makes it more clear for me that the workaround isn’t ideal in this use case!

7

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