Powder

Runtime settings

Change non-sensitive operational controls without rotating a secret or redeploying the Worker. Saved values apply to this environment and override its deployment defaults.

Using deployment defaults

Your first save creates the live admin override. No credentials are exposed here.

Env fallback

Safety and delivery

Controls that decide whether Powder may take real customer-facing or financial actions.

Gmail

Inbound and outbound controls are separate so mail can be observed before Powder is allowed to reply.

Models and routing

Model identifiers select the provider track by prefix. Credentials remain deployment-managed secrets.

Normal customer conversations and general generation. The list matches Powder's current Bedrock and OpenAI routes.

Complex and merged-workflow conversations. Uses the same supported generation models.

Anthropic-class model used only by the legacy classifier routing path.

Primary workflow/article router. Kimi uses Workers AI; Claude alternatives use Bedrock.

Bedrock-class model used when the OpenAI track is unavailable.

Conversation timing

Tune batching and session lifetimes without a Worker redeploy.

Wait before processing a short greeting so fragmented follow-up messages can join the same turn. Zero processes immediately.

ms

Allowed range: 0–30,000 ms.

Wait before processing regular WhatsApp messages. Zero processes immediately.

ms

Allowed range: 0–30,000 ms.

How long a widget session token remains valid; the widget refreshes at 80% of this lifetime.

seconds

Allowed range: 300–86,400 seconds.

Identity verification

Bounded security controls for widget email and phone verification.

Email codes use this lifetime. Twilio phone codes are always capped at 10 minutes by the provider.

seconds

Allowed range: 60–3,600 seconds.

How long successful email or phone verification grants Tier 2 access.

seconds

Allowed range: 300–604,800 seconds.

Minimum wait before another code can be sent. It cannot exceed the selected challenge lifetime or Twilio's 10-minute phone-code lifetime.

seconds

Allowed range: 10–600 seconds.

Fail a Powder-owned email OTP challenge after this many incorrect checks. Twilio controls phone-code attempts separately.

attempts

Allowed range: 1–10 attempts.

Advanced runtime

Experiment and budget controls for features that do not store credentials.

Maximum analytics-only shadow executions per day. Zero removes the cap; disable shadow configs to stop runs.

runs/day

Allowed range: 0–100,000 runs/day.

Use deterministic English copy or compose handoff messages with the configured model.

Use regex matching or model classification for replies inside the channel handoff flow.

All changes are saved.
What stays in deployment configuration?

Credentials

API keys, OAuth signing material, database URLs, Twilio tokens, service-account JSON, webhook secrets, and connector authentication values.

Trust boundaries

Allowed origins, managed mailbox identities, Access audiences, public service origins, relay signing, and environment identity.

Infrastructure and rollout

Queues, Durable Objects, storage bindings, Gmail project/topic wiring, relay topology, file-config authority, and the conversation-summary cutover gate.