Skip to main content
In a cloud deployment, configuration, the service account, and network access all belong to the server. Complete an APIONE conversation before connecting DingTalk or other channels.

Prepare the deployment

  1. Select an available OpenClaw image in Alibaba Cloud, or follow OpenClaw’s installation instructions. Use the console for current instance specifications, pricing, and image versions.
  2. Identify the actual user and home directory running OpenClaw.
  3. Back up that user’s ~/.openclaw/openclaw.json, keeping gateway and channel settings.
  4. Create a dedicated APIONE key and confirm outbound HTTPS access to api.apione.ai.

Configure models

Follow the OpenClaw guide to merge models.providers.apione and set the default model to apione/YOUR_APIONE_MODEL_ID. The service may run as admin, another user, or inside a container. Edit the configuration it actually reads.
Send a simple message using the local TUI or a protected dashboard. Confirm APIONE usage before proceeding.

Connect DingTalk or other channels

Configure the application ID, secret, and bot according to the current channel plugin. For DingTalk AI cards, create a template and provide the template ID and required card-writing and streaming-update permissions. Test a direct conversation before groups and streaming messages. Model API keys, DingTalk credentials, and gateway credentials are separate. Do not expose the management port publicly just to test inference.

Optional search and browser tools

Search services require separate accounts and credentials; their fees are not part of APIONE inference charges. Browser automation requires a browser and dependencies on the server. Set its executable path and headless mode for the image, then check openclaw browser status. Install appropriate fonts if needed. Model integration does not require disabling the browser sandbox.

Troubleshoot in order

Check server connectivity, then APIONE inference, then the gateway, then channel callbacks. This separates credential, service-user, model-access, and messaging-platform problems.
Integration directory · Choose a model · Troubleshooting