An Instagram comment-to-DM flow needs more than a keyword
Choose the correct Meta login route, respect the initial-reply window and track retries before promising a guide in someone's Instagram messages.

Someone comments guide beneath a Reel and receives a private message containing the promised link. The visible interaction is short. Behind it, the business has to associate the right comment with the right resource, then track whether its reply was accepted.
Instagram provides supported APIs for this kind of private reply. The implementation depends on the login route and the permissions granted to the app. An old tutorial can become misleading when it treats one route's setup as a universal requirement.
Choose the login route before copying an endpoint
Meta's Instagram API changelog records the introduction of Instagram Login in July 2024, with no linked Facebook Page required for that route. Its permissions and API host differ from the Facebook Login setup.
Meta's current Instagram Messaging private-reply guide describes a Facebook-linked implementation. It uses a Page access token and the comment ID in a request to the Page's messages endpoint. That is a specific configuration, with its own permission requirements.
Select one documented route for the application. Keep its token type with the corresponding endpoint and account identifiers. Mixing a token from one setup with the request path from another makes a permissions error difficult to diagnose.
Access for an app's testers also differs from access for an external customer. Complete the review and access process required for the intended deployment before treating a successful developer test as a finished integration.
The initial reply has a defined window
The private-reply guide permits one message in response to the comment. For posts and Reels, it must be sent within seven days of the comment. Live comments have a different limit: the reply must be sent during the broadcast. Continuing the ordinary conversation requires the recipient to respond, opening the applicable 24-hour window.
The seven days therefore describe when that first reply may be sent. They do not mean the message itself disappears a week later. A comment requesting a resource also leaves an ongoing promotional sequence to be considered separately.
Write the first message so it completes the request. If the Reel promises a guide, include a working route to that guide. Requiring another interaction merely to discover what was promised adds a failure point to a simple delivery task.
A recipient who does not follow the professional account may receive the message in Requests. Keep the public explanation of the automation accurate enough that someone knows where to look without promising instant delivery to their main inbox.
Match the event before sending anything
A workflow needs to know which post the rule covers. The same word can appear in ordinary discussion beneath a different Reel. Match the media identifier as well as the intended keyword before selecting a reply.
Keep the resource mapping separate from the event-processing logic. One post can point to a writing guide while another points to a template. Updating a resource URL should be an inspectable change to that mapping.
An LLM is unnecessary for an exact keyword rule. A deterministic match is easier to explain when someone asks why a message was sent. If the business later needs to interpret free-form requests, it can evaluate that new requirement using real examples.
Preserve enough information to explain a decision without retaining unrelated conversation content indefinitely. An event record can identify the rule version and the comment processed. Define how long that record is needed for support before accumulating a permanent copy by default.
Receive the event separately from the outbound result
n8n's Webhook node provides test and production URLs with configurable response behavior. Its HTTP Request node can make the subsequent authenticated API request. These are general integration components; their presence does not supply the app's Meta permissions.
Validate the incoming request using the platform's documented verification mechanism. Record an accepted event durably before acknowledging it for later processing. If the event is acknowledged and then lost from memory, the business can lose the request while the sender believes it was received.
Use the account and comment identifiers to recognise an event already being handled. A repeated notification should return to the existing record. Concurrent runs need an atomic claim on that record so both cannot independently decide that the comment is new.
After sending, store the API's returned message identifier with the result. If a connection fails before the response arrives, keep the state uncertain until it can be reconciled. Blindly retrying a send can create another attempted message after the first request was already accepted.
Test the failure that the demonstration skips
Meta publishes rate limits for its Graph and messaging APIs. The limits depend on the API and account context. A workflow should handle a refusal as an observable outcome with a retry decision, instead of marking every completed execution as a delivered message.
Test an unrelated comment first. Then replay one eligible event to inspect duplicate handling. Check the actual recipient experience from an account that is not following the business, and confirm that an expired comment cannot enter the initial-reply path.
Finish by opening the resource link from the received message. A successful API response can coexist with a broken download URL. The requested guide is delivered only when the person can reach it.