Overview
Answer private messages to a Facebook Page with a Voiceflow agent. A developer-hosted HTTPS relay receives Messenger events, runs the agent and returns text to the same Page-scoped customer.
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.
Create the app and select the Page
Create a business app in Meta for Developers and add the Messenger use case. In its Messenger settings, connect the Facebook Page that customers will message. Have an administrator grant the requested Page permissions and generate its Page access token. Save the Page ID as META_ACCOUNT_ID and the token as META_ACCESS_TOKEN.
Prepare app access
Use app-role testers for development. To receive messages from customers without an app role, request Advanced Access for the required permissions through App Review, complete the business verification Meta requests, and put the app in the applicable live state. Supply a privacy policy, data deletion instructions and the review test journey.
Use a durable Page token derived through the supported login flow. Access can be revoked when the administrator, Page permissions or business configuration changes; “long-lived” is not a guarantee against revocation. See Messenger webhooks and access levels.
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.
Set the Page webhook callback to https://YOUR_HOST/webhook with META_VERIFY_TOKEN, then choose Verify and save. Subscribe to messages, message_deliveries and message_reads. In the Messenger app settings, subscribe the selected Page to your app. To make the Page subscription explicitly, save and run:
Expect success: true. The relay checks each POST’s raw-body HMAC with your app secret, scopes events to your Page and ignores message echoes. Postbacks and persistent menus require a separate action adapter; subscribing to them does not implement their behavior.
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.
Automated standard replies stay within the 24-hour messaging window. The sample refuses stale queued replies; it does not apply human-agent tags or marketing permissions to AI output. See Messenger’s messaging policy.
The receive endpoint acknowledges persisted events before running the agent. Meta expects prompt acknowledgment and can redeliver failed notifications; mid prevents a second agent turn. This recipe is a private Page conversation, with no Facebook group or public comment support.
Test a customer conversation
Verify the reply in the destination you installed.
Send a real platform message
From an app-role test account, open the Page in Messenger and send your prepared question. Expect the Page to answer in the same private 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
Send a second question from a different test account. Its answer must not include the first customer’s context; run the included signed-fixture tests and confirm only one turn.
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.
Check Page subscription as well as app-level webhook configuration, Page-token validity, the Page ID and Advanced Access. If delivery succeeds only for app admins, resolve app review before inviting customers.
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 App Review and the applicable live configuration, then test with an authorized account that has no app role. Keep the approved Page and privacy/deletion endpoints available.
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.