@laburen/openclaw-plugin-whatsapp-api 0.7.0 → 0.8.0

package/index.js

@@ -1432,26 +1432,8 @@ const USER_PHONE_CONFIG_KEY = "userPhoneNumber";
 const LABUREN_API_KEY_CONFIG_KEY = "laburenApiKey";
 const USAGE_PATH = "/api/usage";
 const POST_TIMEOUT_MS = 3e3;
-/**
-* OpenClaw classifies each run by `trigger`. Only `user` (and `manual` admin
-* actions) should be billed as real product usage. Background runs initiated
-* by the runtime (`heartbeat`) or by scheduled jobs (`cron`, `memory`,
-* `overflow`) must be reported under a separate feature so the backend can
-* apply a different billing policy.
-*
-* Without this mapping every heartbeat and every duplicated wa-api cron tick
-* (which both fire every 30m) was charged to the user as `openclaw_run`,
-* draining credits without any real interaction.
-*/
-function resolveFeatureFromTrigger(trigger) {
-	switch (trigger) {
-		case "heartbeat":
-		case "cron":
-		case "memory":
-		case "overflow": return "heartbeat_run";
-		default: return "openclaw_run";
-	}
-}
+/** Fallback when OpenClaw's runtime did not surface a `trigger` in the hook ctx. */
+const DEFAULT_FEATURE = "openclaw_fallback";
 function resolveUsageIngestUrl() {
 	let baseRaw;
 	try {
@@ -1509,7 +1491,7 @@ async function handleForwardLlmUsage(event, ctx) {
 	const cacheWrite = usage.cacheWrite ?? 0;
 	const total = usage.total ?? input + output + cacheRead + cacheWrite;
 	const body = {
-		feature: resolveFeatureFromTrigger(ctx.trigger),
+		feature: ctx.trigger ?? DEFAULT_FEATURE,
 		runId: event.runId,
 		sessionId: event.sessionId,
 		userPhoneNumber,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@laburen/openclaw-plugin-whatsapp-api",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "type": "module",
   "description": "WhatsApp API channel plugin for OpenClaw",
   "main": "index.js",