whatsapp-subscription-manager

WhatsApp subscription manager — add, pause, resume, remove, list, validate

Manages WhatsApp subscriptions through the wfnexus API and reads every change back. Expose it over MCP or a hook so an agent or a chat can subscribe a workflow to a group without opening the UI.


Source	`templates/whatsapp-subscription-manager/workflow.yaml`
Category	`debugging-ops`
Trigger	called by other workflows · manual (`wfx run`)
Steps	3
Human approval before	`approve`
Providers named	default (`WFX_DEFAULT_PROVIDER`)

Use it

wfx templates whatsapp-subscription-manager
wfx new whatsapp-subscription-manager --as my-whatsapp-subscription-manager
wfx dryrun my-whatsapp-subscription-manager

What it does

Adds, updates, pauses, resumes, removes, lists or validates a WhatsApp subscription through the wfnexus API, then reads it back to prove the change. Removing one, or letting everyone start an auto-replying workflow, waits for a person’s approval.

What you fill in

nothing required — WFX_API is set for every run; set WFX_TOKEN in the project env if your API needs a bearer token
expose it: wfx expose mcp whatsapp-subscription-manager (and/or hook)

Inputs

Input	Type	Default	Required	Meaning
`action`	string		yes
`name`	string
`channel`	string
`chat`	string
`workflow`	string
`version`	string
`events`	string
`interval`	string
`skills`	string
`instructions`	string
`responsePolicy`	string
`memory`	string
`mode`	string
`activation`	string
`allow`	string
`owner`	string

Steps

#	Step	Kind	Skills	Gates
1	`plan` Check the request against the live subscriptions	shell (`run:`)		`exitCode` = `2` → fail
2	`approve` A person approves	shell (`run:`)		human approval first
3	`apply` Apply and read it back	shell (`run:`)		`exitCode` = `5` → fail

Human gates

approve waits for wfx approve <run-id> (or wfx reject <run-id> -m "why") before it runs.

Real result