Console
Documentation/Integration recipes

Integration recipes

Connect n8n, OpenClaw, Hermes or your own process.

The integration examples in the repository use the same public API and event contract as every other client. They do not rely on browser automation or unofficial WhatsApp sessions.

n8n

Use an HTTPS Webhook trigger, verify Sqkii's raw-body signature in a trusted receiver, and forward verified events to the workflow. The example workflow illustrates event filtering and a response request; import it, bind your credentials and configure a reachable receiver before activating it. Do not embed tokens in exported workflow JSON.

OpenClaw

OpenClaw stores MCP definitions under mcp.servers. Use the stdio configuration in examples/openclaw, supply a scoped key through its secret mechanism, and verify with openclaw mcp doctor sqkii-whatsapp --probe. Run the event-feed bridge for continuous inbound processing. The generic bridge delivers verified API events to a local customer-owned harness endpoint. Check your installed OpenClaw version's endpoint and tool configuration before enabling the adapter.

Hermes

Hermes stores MCP definitions under mcp_servers in its active config.yaml. Use examples/hermes/config.yaml with environment-backed credentials for interactive tools, or the generic event bridge for a running Hermes harness. The repository deliberately does not assume that every Hermes distribution exposes the same local HTTP endpoint.

Your own harness

Implement one receiver that accepts event envelopes and one sender using a scoped SDK client. Deduplicate incoming events before invoking tools. Preserve number and conversation scope throughout your agent run.

See repository examples under examples/n8n, examples/openclaw, examples/hermes, examples/typescript and examples/python.

Configuration sources checked 18 November 2026: OpenClaw MCP, Hermes MCP configuration.

Prepared 18 November 2026 · Sqkii Pte. Ltd.