We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Webhook doesn't notify
Hi,
I deployed my javascript lambda function on AWS. The function works great when using Postman. Also, when I add the link to my AWS function to the Webhook URI in my Dropbox App, it enables, meaning that the challenge is being accepted. Yet, when I add a new file to my Dropbox, it doesn't notify my function.
Is there any known problem caused by using AWS? Or can it be anything else causing this?
There shouldn't be an issue with AWS in particular, but there are a few reasons you may not be seeing webhook notifications.
1) Have you "linked" or "connected" or "authorized" the app to your account? Webhook notifications will only be sent for changes in accounts that are connected to the app.
When you create a Dropbox API app as a developer, it is not automatically connected to your account as if you were an end-user of the app. You will need to connect to it, as covered in the OAuth guide.
2) Are you making changes in the same account that you've linked to the app? Similar to the above, make sure you're making changes in the correct account.
3) If your app is registered for the "app folder" permission, are you making changes in the special app folder created for the app? Webhook notifications will only be sent for changes that the app can access, so Dropbox won't send webhook notifications to an app folder app for changes outside its app folder.
4) Are you sure you've properly configured your server to respond to webhook notifications? It may be helpful to add some logging along that code path to see where it may be breaking down.
- Greg-DB
Dropbox Staff
There shouldn't be an issue with AWS in particular, but there are a few reasons you may not be seeing webhook notifications.
1) Have you "linked" or "connected" or "authorized" the app to your account? Webhook notifications will only be sent for changes in accounts that are connected to the app.
When you create a Dropbox API app as a developer, it is not automatically connected to your account as if you were an end-user of the app. You will need to connect to it, as covered in the OAuth guide.
2) Are you making changes in the same account that you've linked to the app? Similar to the above, make sure you're making changes in the correct account.
3) If your app is registered for the "app folder" permission, are you making changes in the special app folder created for the app? Webhook notifications will only be sent for changes that the app can access, so Dropbox won't send webhook notifications to an app folder app for changes outside its app folder.
4) Are you sure you've properly configured your server to respond to webhook notifications? It may be helpful to add some logging along that code path to see where it may be breaking down.
Thanks for your reply. I am pretty positive that step 1-3 ain't the problem. It has to be step 4. When I hosted the lambda function on Netlify it worked properly. When I tried to migrate the function to AWS, these problems started to appear.
When I enable the webhook URI in the Dropbox console, AWS ClodWatch logs confirms that my lambda function received, listened and executed the function. Also, it works great with Postman. But when I add a file to my Dropbox folder, the AWS CloudWatch logs don't register any attempt to listen to the webhook from Dropbox. So i'm trying to figure out why my aws lambda function doesn't listen to webhooks.
Do you find something that could be helpful to fix the problem with AWS Lambda? I'm having the same issue,
- I uploaded it to Netlify and it worked properly.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
