Which webhook fires when a reply is accepted?

JA Jamal Reed vor 4 Monaten Gelöst

I want to notify an external system whenever a reply is accepted as the answer in a Q&A space. I see post and reply created events — is there a dedicated accepted-answer webhook, or do I listen for an update?

2

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Go to your profile, then Edit, and scroll to the relevant section. The option you are looking for is there. If the section is hidden, confirm you are on a recent version — some controls were added in 1.4.

Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.