n8n · Help

Instagram DMs never reach n8n, but test webhooks do?

Instagram test events work but real messages are missing? Trace event delivery, the public route and the n8n production endpoint.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

A verified Instagram callback or successful request you send yourself does not establish delivery of real messaging events to n8n. First compare the configured callback with the published workflow's production webhook. Then trace one permitted test message by timestamp at the sending service, public ingress and n8n. If no delivery attempt exists, investigate the actual API variant before changing downstream workflow nodes.

Source basis: Q1 · Q2

Applies to
The original case uses self-hosted n8n, a public tunnel and Instagram Login. It establishes no universal fix; requirements from other Instagram integration variants cannot be assumed.
How to verify the result
One real permitted test message is traceable through all three observation points to harmless processing, while signature verification and the intended access controls remain enabled.
Your first check

Is a delivery attempt for a real message visible at the public endpoint?

The callback has been verified and a manual test reaches n8n. Real Instagram messages still produce no visible execution. A useful investigation needs one real test event with a timestamp and separate observations from the sending service, the public endpoint and n8n.

Why a successful test is insufficient

An original report describes this situation with self-hosted n8n, a public tunnel and an Instagram Login integration. It does not establish a universal fix. Q1 n8n distinguishes test and production webhooks; an editor test listener does not replace the published production endpoint. Q2

A request you send yourself also checks only the route you used. It does not prove that the service attempted to deliver a real messaging event for the intended account. Avoid combining instructions for different Instagram integration variants without establishing which one your application uses.

Locate the missing stage

  1. Define a specific event. Send a permitted test message between accounts appropriate for your setup. Record the timestamp and timezone, application identity, receiving account and expected event type. Use a neutral test message instead of personal conversation content.
  2. Compare production addresses. Compare the callback stored in the application with the Production URL of the published workflow, including path and expected HTTP method. Successful callback verification is not the same operation as subsequent event delivery.
  3. Inspect the service-side evidence. Where the relevant interface provides them, examine event subscriptions, connected account, app mode and delivery information. If no delivery attempt exists, investigate the prerequisites of that specific API variant first. Do not copy permission names from another integration model.
  4. Correlate ingress logs. Search reverse-proxy or tunnel logs for the timestamp and path. If a request arrives, record its method, response status and forwarding destination. If it does not, a processing node behind the n8n webhook is not yet the first place to change.
  5. Account for n8n visibility. Check workflow identity, published version and execution-list settings. A missing visible execution alone does not prove that no request reached the public endpoint.

Complete a controlled end-to-end check

A real test should be traceable from the event to a harmless intended result. Keep correlation data and prevent automatic replies during investigation. Do not remove signature or access controls merely to obtain an apparent success. After correcting the identified stage, repeat one controlled event and compare all three observation points again.

Frequently asked questions

Should I simply switch the app to live mode?

This symptom does not establish that requirement. Account type, API variant, approved access and test setup must fit together. Check current requirements for the exact configuration you use.

What makes a useful handover?

Provide an anonymised connection diagram, n8n version, callback path, application and account type, and a timestamp with evidence from the three stages. Access tokens and complete private message histories are unnecessary.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0158 with KAN KAI WORKS.

Support with this issue

We investigate n8n using your error message, versions and a narrowly scoped example.

Describe your case →Related service: AI & automation

Sources

Sources checked on 5 November 2026. Individual reports do not establish general prevalence.