Account Activity: valid webhook and subscription, but no activity coming through

[TaylorKrusen]

Hello! Using the ‘Account Activity Dashboard’ (great resource, btw) with localhost and Ngrok, I was able to successfully create a webhook, a subscriber, and see the webhooks coming through on the Live Activity tab.

However, using AWS Lambda, I can’t see any activity coming through after successfully creating a valid webhook and subscription. I can see the active webhook and it responds to any challenges I issue. I can also see the active subscription and verified that it’s for the correct application ID. Unfortunately, no activity is coming through!

I’m not really sure where to look next… any recommendations?

[LeBraat]

I’m glad to hear that you like the dashboard!

Unfortunately I’m not too familiar with AWS Lambda. I will check with some colleagues to see if they can help out.

[TaylorKrusen]

Appreciate it! As an FYI, I’m also using the Account Activity Dashboard for visibility into my webhook, subscription, and activity even when I’m creating the webhook on Lambda. That’s how I can see that no webhooks are making it through. However, I’m using Postman to create the Twitter webhook on Lambda and subscribe to it.

[LeBraat]

I also have used Postman and Insomnia to register my webhook URL and for a couple of other actions with the Account Activity API. I just haven’t played around with Lambda yet.

So far, no luck with internal knowledge of Lambda.

[TaylorKrusen]

Success!! It’s working now. Posting some details about how I fixed it in case anyone else runs into a similar problem.

I was relying on the ‘Live Activity’ section of the Account Activity Dashboard to see whether or not webhooks were coming through. That was a mistake because the webhooks were POSTing to the callback I registered on my webhook (not localhost where the Account Activity Dashboard was running).

The issue wasn’t with the Twitter webhook at all (which was working and valid). The problem was with my Lambda setup. Specifically, the ‘role’ that was executing the Lambda function didn’t have the appropriate permission policies to write to the CloudWatch logs. Once I fixed the permissions and my logs started writing, I could see the webhooks coming through from my account activity.

Hope my mistake can help someone later. Future troubleshooters: feel free to connect with me on Twitter if you need a hand using Lambda for your Twitter webhook.

[LeBraat]

[LeBraat]

Thanks for the follow up @TaylorKrusen!
Glad to hear that you got everything working properly!

[LeBraat]