Overview

Answer private messages to a Rakuten Viber bot with a Voiceflow agent. This walkthrough uses the Bot API, a commercially provisioned bot and your own signed-webhook 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.

1

Apply for and provision the bot

Apply through Rakuten Viber’s bot program. Complete the commercial onboarding before implementing a public destination. You need an active Viber administrator account and an active bot; a personal Viber account alone does not expose this API.

2

Collect the app key and bot identity

As a bot administrator, copy the app key from More → Settings → Bots → Edit Info → Your app key, or the Viber Admin Panel where available. Save it as VIBER_BOT_TOKEN. Call get_account_info and retain the returned bot ID:

Use id as VIBER_BOT_ID and retain the bot’s entry URI for testing. Check the name and identity against the commercial account you intended to provision.

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.

1

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.

2

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.

3

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.

After the relay is reachable, save register.mjs, add PUBLIC_URL=https://YOUR_HOST to .env, and run node --env-file=.env register.mjs:

Viber calls the endpoint to check availability. Expect status: 0. The relay validates X-Viber-Content-Signature using the bot token as its HMAC-SHA256 key and acknowledges validation/control events without running Voiceflow. Use a public certificate; self-signed certificates are not supported. See the Bot API webhook contract.

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.

This recipe responds to customer messages. It does not send a welcome message on conversation_started or initiate unsolicited contact. A subscription or permitted user interaction must support your messaging use; an unsubscribed user may be unreachable.

Non-200 callbacks can be redelivered, so keep the original message token across retries. Viber uses numeric status codes in otherwise successful HTTP responses; status: 0 means API acceptance. Later failed callbacks must still be investigated. The sample uses smaller text chunks than the API’s text maximum and records accepted chunks before proceeding.

Test a customer conversation

Verify the reply in the destination you installed.

1

Send a real platform message

Open the bot’s approved Viber entry link on a test device, subscribe/start the conversation and send your support question. Expect a reply from that bot in the same chat.

2

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.

3

Check this platform’s delivery behavior

Replay an authorized signed fixture whose message_token exceeds JavaScript’s safe integer range. The deduplication key must retain all digits and generate 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 commercial activation, the app key, valid HTTPS certificate and bot entry URI. Inspect both the send response’s numeric status and later failed callbacks; HTTP 200 alone is insufficient.

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.

1

Approve the production destination

Confirm commercial activation and the approved customer entry link, deploy the reviewed bot credentials, then repeat the Viber test from an authorized subscriber. Honor unsubscribe and provider restrictions in any later outbound feature.

2

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.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.