Intercom article reaction negative feedback alert webhook returns 500 error

TL;DR

Fix this in Intercom by acting on the exact symptom first: make the receiving endpoint accept the reaction payload, return a success response before doing any slow processing, log the payload that failed, and replay one negative reaction to prove the alert fires. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Intercom article reaction negative feedback alert webhook returns a 500 error

Use this when

• Work in Intercom shows this exact symptom: Intercom article reaction negative feedback alert webhook returns a 500 error.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Intercom, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: make the receiving endpoint accept the reaction payload, return a success response before doing any slow processing, log the payload that failed, and replay one negative reaction to prove the alert fires. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Intercom that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Intercom article reaction negative feedback alert webhook returns a 500 error

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Intercom article reaction negative feedback alert webhook returns 500 error

The how to phrasing for the same problem in Intercom. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Intercom troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The handler tried to create the alert synchronously and raised on a reaction payload with no article rating detail, so Intercom recorded a server error and dropped the alert.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Intercom at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_9kOH7px2gFtQ5RDyyku0lg