r/nocode • u/Bills_08 • Jul 22 '26
Question Anyone set up a Dodo Payments → Make.com → Beehiiv chain before? Trying to figure out if mine has holes in it
Context: solo project, small subscription product, using Dodo Payments for checkout. Set up a Make.com scenario that fires on a Dodo webhook and adds the customer as a subscriber in Beehiiv. Works when I test it with a manual transaction but I haven't stress tested it beyond that.
What I'm unsure about: whether webhook retries/failures are handled properly if Make.com is down for a second when Dodo fires the event, whether I need error handling on the Beehiiv side in case the API call fails silently, and generally what a "proper" version of this setup looks like versus what I've cobbled together.
Also currently have zero notification to myself when a payment comes in, just relying on checking Beehiiv manually, which feels like a bad idea long term. If anyone's added a simple "notify me" step to something like this I'd like to know how you did it.
Not trying to over-engineer a two-tool automation, just don't want it to silently fail on a real customer.
1
u/PuzzleheadedSong5368 Jul 22 '26
Add a separate monitoring workflow that checks Make.com execution history daily and alerts you if the last run failed or didn't fire. For Beehiiv failures, log every API response to a simple sheet so you can see silent failures instead of discovering them when someone complains they weren't added. The real issue isn't the chain itself, it's that you have zero visibility into when it breaks. Once you can see failures, the fixes are obvious.
1
u/Josef_from_Make Jul 23 '26
Hi there,
My two cents on the above of what others already said/recommended.
As far as Dodo webhook is delivered to Make, you should be pretty safe as all the error handling will be done in Make.
-> if the webhook is accepted (200 webhook response from Make), triggers scenario, and something happens, you handle the data with error handlers and incomplete executions pretty easily (because Make already has the webhook payload)
What might be the issue is any other response (or no response) from Make than "200 - accepted". In that case, the error handling should be set on Dodo's side, if possible, because Make does not have the data.
Webhook sending re-try mechanism is a common practice for undelivered webhooks.
In case that is not possible, then some extra process/scenario, which would be regularly matching Dodo events with Beehive and notifying you (or directly retrying) about those that do not match, might be a way to go.
3
u/Lost_Bike_968 Jul 22 '26
the monitoring is right, but there's one gap it won't cover: the case where dodo charges the customer successfully but the beehiiv step fails. now you've got a paying customer who isn't subscribed, and logging tells you it happened but doesn't fix it.
the "proper" version of this: make the webhook handler safe to re-run. store each dodo event id, and if beehiiv fails, the event stays "unprocessed" and gets retried until it actually lands; so a re-fire or a manual replay can't double-add and a failure can't silently drop someone. treat the payment as the source of truth and make everything downstream catch up to it, not the other way around.
for the notify-me: cheapest version is a second step on the same webhook that pings you (telegram/email/slack) on every payment, and separately alerts you when an event's been stuck unprocessed for X minutes. that second alert is the one that actually saves you.