npx zavudev functions

npx zavudev functions (alias fn) drives Zavu Functions — your TypeScript running on every messaging event. The most-used subcommands are also available at the top level: npx zavudev deploy is npx zavudev fn deploy.

Scaffold

terminalCopy
npx zavudev fn init --name order-bot --template blank

Writes index.ts, a package.json declaring @zavudev/functions, a tsconfig.json, and .zavu/config.json holding the function's id. Run npx zavudev fn init --help for the current template list.

To start from a working agent instead of a blank file, see npx zavudev agents pull.

Deploy

terminalCopy
npx zavudev deploy

CodeCopy
› Deploying Order Bot (order-bot)…
  deployment id: nx7v0h30epeh2s7ppxcn9mpan58b6yre
› status: active
ℹ Agents synced:
    + Bella
ℹ Tools synced:
    + lookup_order
✓ Deployed in 11.5s

The summary lists what the deploy did to your agents and tools. Read the lines above the ✓ — they print before the success line. There is no ✓ at all, and the command exits non-zero, in two cases:

1. Your declarations were not synced. The Lambda is live and its agents and tools are unchanged.
2. Your declarations synced and something in them cannot work — an agent no connected sender can reach, for instance. Everything deployed; the result is not usable as-is.

A CI job gating on the exit code will fail on both, which is the intent: the second one is the deploy that otherwise looks green and answers nobody.

Warnings you may see, and what they mean:

npx zavudev fn push updates the draft without deploying. Useful to save work in progress; nothing changes in production until deploy.

Run it locally

terminalCopy
# Call one tool handler directly, with no deploy:
npx zavudev fn invoke --tool lookup_order --args '{"orderId":"ORD-001"}'

# Or dispatch a synthetic event at your default export:
npx zavudev fn invoke --event message.inbound \
  --data '{"from":"+14155551234","text":"hola"}'

This is the cheapest feedback in the product: it exercises your handler exactly as production will, in milliseconds, without deploying or spending anything.

Logs

terminalCopy
npx zavudev fn logs            # recent invocations
npx zavudev fn logs --tail     # follow

Run it from the function's directory. Lambda's own noise is filtered out and internal identifiers are redacted.

Secrets

terminalCopy
npx zavudev fn secrets list
npx zavudev fn secrets set STRIPE_KEY sk_live_…
npx zavudev fn secrets set STRIPE_KEY --from-file ./key.txt
npx zavudev fn secrets unset STRIPE_KEY

Values are write-only: list shows the last four characters, never the secret. Reach them in your handler with process.env.STRIPE_KEY.

Triggers

terminalCopy
npx zavudev fn triggers list
npx zavudev fn triggers events                    # what you can subscribe to
npx zavudev fn triggers add --events message.inbound
npx zavudev fn triggers toggle <triggerId> --off
npx zavudev fn triggers remove <triggerId>

A trigger subscribes the function to an event, optionally scoped to one sender. A function that only declares an agent and its tools needs no triggers — the agent path invokes it directly.

Versions and rollback

terminalCopy
npx zavudev fn versions list
npx zavudev fn rollback <version>

Every deploy is a version with its own record. rollback republishes a previous one's source and dependencies; it always asks for confirmation. Secrets are not rolled back.

Delete

terminalCopy
npx zavudev fn delete            # in the function's directory
npx zavudev fn delete <functionId>

Removes the function and everything it owns — its triggers, secrets, deployment history, and the agents and tools it manages. It asks you to type the slug first, because there is no undo.

Where to go next