- Threads replies delivered as comment.received: Replies to your Threads posts now arrive through the same
comment.receivedwebhook used for Instagram and Facebook comments, so you can handle them with the same code path. No reconnect is needed for existing accounts since the required permission is already included by default. - Self-replies are filtered out automatically: If your account replies to its own Threads post (for example, via an auto-reply), that reply is skipped so you don't end up processing your own messages in a loop.
- Known limitation documented for cross-thread replies: A reply to your own reply under someone else's Threads post isn't delivered, since it belongs to another account's thread; this is now called out in the docs so it isn't a surprise.
- Threads docs updated: The Threads configuration page now has a dedicated Comment Webhooks section covering requirements (public accounts, Managed Keys), behavior differences from other networks, and the fact that Threads doesn't send an author ID on replies. The webhooks page also lists Threads replies as a supported
comment.receivedsource.