Web Push Notification Don't Work in Backend Workflows

[pwharker]

I have a test page that allows me to create push subscriptions and send push notifications. That is working well. BUT what I want is to Schedule API Workflow so I can create scheduled notifications. Nothing I seem to do will make a call to Send Push Notification inside a Schedule API Workflow.

Will the plugin work from Backend Workflows?

Paul

[Stephan]

Hello @pwharker,

Thank you for reaching out to us.

Yes, the Zeroqode Push Notifications plugin does support sending notifications from backend workflows, including scheduled API workflows. If your push notifications are working properly on a test page but aren’t triggering as expected in a scheduled workflow, there are a few common issues you can troubleshoot:

1. VAPID Keys: Ensure that the VAPID public and private keys are correctly set in both the frontend and backend workflows. If they are not correctly configured, the notification may fail to send.
2. Push Subscription Format: Verify that the push subscription data (endpoint, keys, etc.) is correctly saved and retrieved in your backend workflow. Double-check that you’re passing the same data format in your scheduled workflow as in your test page.
3. Logs & Debugging: Check your server logs for any errors or warnings that occur when the scheduled workflow is triggered. This can often reveal missing parameters or other configuration issues.
4. Delay in Scheduling: Sometimes, when scheduling workflows, there might be a delay in execution. Ensure that the scheduling timing is correct and that the backend workflow triggers at the expected time.
5. Backend Workflow Triggering: Test your backend workflow by manually triggering it, bypassing the schedule, to ensure that the push notification is properly executed.

Could you please check these aspects and let me know about your progress?

Thank you, and I look forward to your reply.

Best regards,
Stefan
Support Team
Browse all Zeroqode Plugins for Bubble

[pwharker]

Hi Stephan,

I checked your suggestions and put together a definitive test: Both methods write to an AppLog when fired, with the pertinent details. One happens between the button click and the call to the Send Push Notification method on the plugin, and the other happens inside the API call workflow just before the call to the Send Push Notification method on the plugin. The data passed to the plugin is shown here (with VAPID keys partially redacted).

As you can see, the values are IDENTICAL in both cases.

[Stephan]

Hello @pwharker ,

Thank you for your message.

From your image, I see that you have set up the workflow to send push notifications both with the backend API, and it appears to be sending correctly and the values are identical. Can you please let us know if you are you still experiencing any problems with the notifications not being sent, or are there issues with how the method is triggered?

If you are still encountering difficulties, could you please share more details, such as additional screenshots or a screencast showing how you set up the entire process in the backend and what happens when it is triggered in the preview? Also, please check if the VAPID keys are properly configured and valid.

Thank you once again, and I look forward to your reply.

Have a great weekend ahead!

Best regards,
Stefan

[pwharker]

Let’s meet quickly and I can show you. Launch Meeting - Zoom

[pwharker]

Yes, I am experiencing problems. Sorry if I was not clear. The “direct” method works properly. The “API” method (backend workflow) does not. That’s why I set up this test to show you.

Here is the call to the Backend Workflow (Schedule and API call)

[Stephan]

Hello @pwharker,

Thank you for your message, and apologies for the late reply over the weekend.

We have looked further into your concern and found that it could be related to using the plugin on iOS or Mac devices - could you please let us know what device and browser are you using? Also, to further investigate this concern more thoroughly and provide a better answer to your inquiry, could you please add our Support Team’s email to the list of collaborators in your application and share the app’s link with us? This will allow us to examine your settings and replicate the issue on our end to pinpoint the cause.

To add our Support Team as a collaborator, please follow these steps in the Bubble Editor: Settings > Collaboration > Add email support@zeroqode.com.

Additionally, please share instructions on how to reproduce the problem on our side, including the name of the page where the related workflow is located and any relevant configurations. A short description of where to click and user credentials to log in would be very helpful in troubleshooting the reported issue. If possible, please attach a short Loom video (screencast recording) providing this guide.

Thank you for your understanding and cooperation.

We look forward to your reply.

Best regards,
Stefan

[pwharker]

Hello,

I have added support@zeroqode to the collaboration as requested.

1. Load the editor and run as pwharker+kristin@gmail.com from Chrome on Windows.
2. Go to page “push-notification-test”
3. Click “Allow notifications”
4. Click the left “mail” icon (direct). You will get a notification.
5. Click the right “mail” icon (API call). You will NOT get a notification

[Stephan]

Hello @pwharker,

Thank you for your message and for sharing the app.

We have reviewed the backend workflow settings and identified an error related to the “contact email” field. The most probable cause of the issue is the current format of the “contact email” field. Could you please change it to mailto:info@atomikdog.com instead of info@atomikdog.com and see if that resolves the problem?

Thanks, and I look forward to your response.

Best regards,
Stefan

[pwharker]

Hello @Stephan, that appears to have fixed the issue! Thank you.

[Stephan]

Hello @pwharker ,

Thank you for your confirmation!

I’m glad to hear that the previous suggestion resolved your inquiry. Please feel free to reach out anytime you have questions or encounter any difficulties with our plugins—it’s always our pleasure to assist you.

By the way, if you have a moment, we’d greatly appreciate it if you could rate our plugin. Simply go to the Plugins tab in the Bubble editor, search for the plugin by name, and assign the stars you feel it deserves. Your support means a lot to us!

Additionally, if you’re willing to share your overall experience with Zeroqode, we invite you to do so at: Review. Your feedback is incredibly valuable to us and the Bubble community, as it motivates us to continue developing outstanding products and maintaining excellent customer service.

Thank you again, and I wish you an amazing day ahead. If there’s anything more you need or any questions you have, please don’t hesitate to contact me. I’m here to support you.

Best wishes,
Support Team
Browse all Zeroqode Plugins for Bubble