Notifications
Clear all
How To
6
Posts
2
Users
0
Reactions
5
Views
Topic starter
We're currently using callin.io to publish web content to Webflow from Airtable. If I notice that I'm duplicating logic across several different situations, I'd prefer not to have to manage separate versions. For instance, one scenario might be a flow to publish a specific item received from a webhook, and another scenario could be scheduled to monitor for updates and publish them.
How can I consolidate some of my logic?
My initial thought is to trigger a webhook from the scheduled scenario, but I was wondering if there's a more streamlined approach. Has anyone else encountered this challenge and discovered an effective solution?
Posted : 16/04/2022 12:23 am
That’s the most effective method currently available.
Posted : 17/04/2022 9:27 am
Topic starter
I configured a workflow similar to this, and I noticed a significant performance impact. This is understandable, as a webhook execution is expected to take considerably longer than for callin.io to simply process the data. Ultimately, I concluded that duplicating the logic is likely a worthwhile trade-off.
Posted : 18/04/2022 2:47 pm
Even with parallel webhook processing? I'm curious about what you mean by a “huge performance hit.” When does it become significant if calling a webhook causes a slight slowdown, I wonder?
Posted : 18/04/2022 7:34 pm
Topic starter
I was executing the workflow from a button click in Airtable, and then waiting for the webhook response back to the button to show to the user. When I was invoking a webhook from within the workflow, it took a considerable amount of time, making it appear as though it had frozen. Switching back to processing the data within the original workflow resolved this issue.
Posted : 18/04/2022 10:54 pm
Ah yes, if you have a UI element, that could potentially be an issue.
Posted : 18/04/2022 10:55 pm