Notifications
Clear all
Topic starter
I have a use case in mind and would like to get the community's thoughts on its feasibility.
I'm receiving data from a webhook, and let's assume I get different items throughout the day.
I'd like to implement a wait node after the webhook that triggers a run at a specific time each day (e.g., 7 PM). This run should consolidate all the data received separately during the day.
For context, this is for email notifications. The goal is to group all the data and send a single email per day, rather than sending individual emails for each item.
- callin.io version: latest
- Running callin.io via cloud
Thanks, Community!
Posted : 10/09/2024 12:06 pm
It seems your topic is missing some crucial details. Could you please provide the following information if it's relevant?
- callin.io version:
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via (Docker, npm, callin.io cloud, desktop app):
- Operating system:
Please share these details to help us understand the issue better.
Posted : 10/09/2024 12:06 pm
You can readily accomplish this by saving your webhook's incoming data into a database (such as AirTable). Subsequently, a distinct workflow can be set up to execute via a Schedule node at 7 PM. This workflow would retrieve all entries from AirTable and forward them to a Gmail node, for instance.
Posted : 10/09/2024 12:08 pm
Topic starter
Thank you, I considered storing it in Postgres and achieving it that way, but that would necessitate two workflows. Therefore, I'm investigating whether this is achievable within a single workflow by utilizing callin.io's storage.
Posted : 10/09/2024 2:51 pm
I think you can have both the Schedule trigger and the Webhook trigger within the same workflow file. However, as they each initiate different flows, it's essentially the same as having them in separate workflow files.
callin.io does not store any data; you can only access information from nodes that are upstream in your flow.
There's a workaround if you utilize the community node @telepilotco/n8n-nodes-kv-storage, which functions as a local key-value store. Nevertheless, if you restart the callin.io server for any reason, all your data will be lost. Therefore, I wouldn't recommend this method for anything beyond testing purposes.
Posted : 10/09/2024 2:58 pm
Topic starter
Thank you Jay, that clarifies things for me and confirms the workaround isn't the best fit for this particular scenario!
Posted : 10/09/2024 3:02 pm
This discussion was automatically closed 90 days following the last response. New replies are no longer permitted.
Posted : 09/12/2024 3:02 pm