I want to create an automated workflow that grabs notifications from certain apps on my Android device and puts them into a spreadsheet or database. I’m trying to use make.com for this automation but I’m stuck on the technical setup.
The main issue I’m having is figuring out how to properly configure the webhook or HTTP module in make.com so it can actually receive the notification data when my phone gets a new alert. I’ve attempted to create an HTTP request module but I can’t seem to get it to trigger automatically when notifications arrive.
Has anyone successfully built something similar? I need help with the proper configuration steps to make this work smoothly.
battery optimization killed my setup twice before i figured it out. check if your phone’s power saving modes mess with background apps too - samsung phones are the worst for this.
Built something like this last year for work notifications. The thing everyone misses - Android’s notification access rules are strict now.
You need an app with notification listener permissions first. I went with MacroDroid over Tasker since it’s more reliable for this. Set it to catch notifications from your target apps, then POST the data to your make.com webhook.
For make.com, create a custom webhook module (not HTTP request). Copy the URL and paste it into MacroDroid’s HTTP request action. Send JSON format with notification title, text, and timestamp.
One gotcha - banking and messaging apps block notification access for security. You’ll need to whitelist your automation app in Android’s notification settings.
The flow: App notification → MacroDroid catches it → Sends to make.com webhook → Processes data → Adds row to Google Sheets. Works smoothly once permissions are sorted.
Setting up webhooks in make.com is pretty straightforward once you get the flow. Just create a webhook trigger module and copy the URL - that’s your endpoint. The tricky part is getting Android to send data there reliably. I’ve had the best luck with the Automate app for this. Set it up to watch for notifications, grab the package name and content, then format it as JSON before posting to your webhook. Don’t forget error handling in your Automate flow - network hiccups will kill everything. On the make.com side, add a JSON parser after your webhook to clean up the incoming data, then connect it straight to Google Sheets with an ‘Add a row’ action. Test it with different notification types since some apps send wonky formatting that’ll break your setup. Also, turn off battery optimization for your automation app or it won’t work consistently.
yup, totally! try using Tasker or Automate as the middleman. once set, they can trigger webhooks pushing those notif data to make.com. oh, and don’t forget to check your permissions, they can mess things up big time!
I ran into this exact issue a few months ago. Make.com webhooks need a trigger from your phone - they can’t just listen passively. IFTTT saved me here. Their Android app has way better notification access, and you can set it up to fire HTTP requests to your make.com webhook whenever specific notifications come in. Just make sure your webhook accepts POST requests and format the notification data right in IFTTT before sending. Honestly though, you might want to skip make.com entirely and use Google Apps Script instead. It plays nicer with Sheets and handles webhook processing without the extra layer.