Overview
Answer Instagram Direct messages with a Voiceflow agent using a professional Instagram account linked to a Facebook Page. This walkthrough uses Facebook Login, a Page token and your own relay.
Before you begin
Collect the agent, account and host access.
The example provides public-policy text support. Keep private Voiceflow and platform credentials on the host; a customer’s messaging identity does not authorize access to orders or account records. Have the agent return text only and provide a support route in its instructions. Buttons, audio and Handoff traces need additional adapters; see Adapt agent replies.
Prepare the platform account
Create the exact app or account this relay will use.
Connect the professional account
Create a Meta app with the Facebook Login use case and configure Instagram messaging. Link the professional Instagram account to its Facebook Page. In Instagram, open Settings → Messages and story replies → Message controls → Connected Tools and enable Allow Access to Messages.
Obtain the matching Page token
Have the Page administrator authorize the app with the listed permissions. Use GET /me/accounts with that user token to select the correct Page and its Page token. Then use GET /{page-id}?fields=instagram_business_account with the Page token to obtain the Instagram account ID. Put the Instagram ID in META_ACCOUNT_ID and the Page token in META_ACCESS_TOKEN; do not substitute the Page ID for the Instagram sender.
For development, configure permitted app/account testers. Public customer access requires the relevant Advanced Access, App Review and business verification requested by Meta. Review Meta’s setup against your account’s login flow.
Run the relay
Configure and host the supplied executable example.
Use the configuration file for this platform. Every name below is read by the supplied artifact; IDs identify the resources prepared above. VF_ENVIRONMENT is the Environment alias, not a version label pasted from another project.
Download and configure the relay
On a Linux host you administer, create /opt/voiceflow-messaging and extract the relay archive there. Use Node.js 22.12 or later. Run node --test fixtures.test.mjs first: it generates signed synthetic events and mocks all remote calls, without credentials or live messages. Save the configuration above as .env, replacing every YOUR_ value; restrict it to the service account with chmod 600 .env. Set DATA_DIR to a private persistent directory that this account can write.
The archive includes core.mjs, platform adapters, HTTP/Teams entry points, local fixture tests and a package manifest. Run node --env-file=.env relay.mjs serve. The HTTP relay uses only Node built-ins; it does not need npm install.
Expose the HTTPS endpoint
Point your own DNS hostname to the host. Terminate HTTPS with a valid public certificate and proxy to 127.0.0.1:8080. For example, with Caddy installed:
Replace the example hostname, allow inbound 80/443 for certificate provisioning and keep the relay port private. Use a separate hostname and credentials for testing. Confirm https://YOUR_HOST/health returns ok before registering /webhook.
Keep one process running
After the foreground check, stop it and create a service using the unit below. Keep one process and one writable data directory per installation. Do not run this file store on ephemeral serverless storage or start multiple replicas.
Create the non-login relay service user, give it read access to the application and .env, and ownership of /var/lib/voiceflow-messaging. Confirm /usr/bin/node --version is 22.12 or later, or substitute your actual Node path. Then run sudo systemctl daemon-reload and sudo systemctl enable --now voiceflow-messaging. Expect the service to stay active; keep the HTTPS proxy running through its own service.
The file store is a small single-process starting point. Back it up privately and monitor disk space, queue age and failures. Higher traffic needs a transactional inbox/outbox and per-conversation workers before adding replicas. Session keys and customer text are stored in the data directory; apply your retention and access policy there as well as in Voiceflow.
Register incoming events
Connect the platform to your hosted endpoint.
Configure the app’s Instagram webhook object with https://YOUR_HOST/webhook and your META_VERIFY_TOKEN. Verify and save it, then subscribe to messages. Install the app’s subscriptions on the linked Facebook Page using its Page ID and Page token:
Add INSTAGRAM_LINKED_PAGE_ID to .env with the Page ID obtained above. Expect success: true. The relay validates the raw-body Meta signature and requires object: instagram and the configured Instagram recipient ID. See Meta’s webhook installation steps.
Route conversations and replies
Keep the customer, agent session and reply destination aligned.
The relay hashes platform, destination account, customer/thread, project and Environment into a bounded Voiceflow userID. It creates a session with the private project key, stores the returned sessionKey, launches once, then sends { action: { type: "text", payload: text } } to /v4/interact. Text traces become platform replies. Follow-ups reuse the key; starting a session every message would reset the conversation.
Only customer-initiated private text is implemented. Standard automated replies must remain within the 24-hour window; this sample does not use the Human Agent permission to extend AI replies. Attachments receive a text-only notice, and comments, mentions, story media and group conversations need their own adapters.
Other login flow: Instagram API with Instagram Login can avoid the linked Facebook Page and uses different permissions and host/token contracts. It is an available platform API, but this page does not provide a second walkthrough for it. Keep its credentials separate from this Facebook Login example.
Test a customer conversation
Verify the reply in the destination you installed.
Send a real platform message
From an approved test Instagram account, open the professional profile and send a Direct text question. Expect the reply from that profile in the same conversation.
Check continuity and isolation
Ask a related follow-up, then test with a second authorized customer. Confirm the intended Voiceflow project and exchange in Transcripts. Run node --env-file=.env relay.mjs inspect while the service is stopped to compare event IDs, conversation keys and completion states without printing session tokens.
Check this platform’s delivery behavior
Test an account outside the app’s roles only after review approval. A successful reply to an administrator does not prove public messaging access.
A saved callback, accepted API request or successful Voiceflow Run does not prove this platform conversation. Keep local signed-fixture tests separate from this authenticated customer test.
The callback saves but no reply arrives
Check platform access as well as endpoint connectivity.
Compare the linked Page, professional Instagram ID, granted instagram_manage_messages permission, connected-tools toggle and Page subscription. Mixing Instagram Login tokens with this Facebook Login relay produces a different contract.
A conversation is paused or a reply is duplicated
Reconcile remote effects before resuming the saved job.
Inspect the event’s phase, failedDuring, saved traces and accepted chunks in the private data file. A runtime timeout can occur after a tool action; a send timeout can occur after the platform accepted the message. The sample pauses that conversation and does not retry either effect automatically. Follow Recover failed messages, then repeat the platform test.
Release and maintain the connection
Promote the tested route and keep recovery available.
Approve the production destination
Complete the permission review and live configuration for the Facebook Login route. Use production Page credentials, retain the linked account relationship and repeat the Direct-message test with an authorized ordinary customer.
Release the reviewed agent
Have the Voiceflow owner publish the tested agent to the intended Environment. Deploy that alias and production credentials to the relay, restart its service and repeat the customer test with a fresh customer/session. Existing session keys are not an automatic migration to a new release. Keep the previous deployment and state backup available for rollback.
Rotate, update or disconnect
Maintain both the provider registration and the relay state.
Stop the service before changing .env or running maintenance commands. Rotate the platform credentials using its administrator controls, update the secret file and restart. If a webhook secret changes, update both sides and check a real event. For a release change, drain or reconcile pending jobs first; do not erase the state file to resolve a delivery problem.
To disconnect, disable/remove this callback or uninstall this app in the provider, stop the relay and revoke its unused credentials. Confirm no new events arrive and retain/delete customer state according to your policy. Keep the registration details needed to reconnect. See Pause automated replies for a temporary conversation-specific pause.