rizzforms
Create forms, configure webhook delivery, manage submissions, and generate embed HTML using the RizzForms API and bundled CLI. Use this skill whenever the user asks to add a contact form, feedback form, signup form, lead capture form, waitlist form, or any form that collects submissions and delivers them via webhook. Also use when the user mentions RizzForms, wants to check form submissions, manage webhooks, or integrate a form backend into their site — even if they don't say "form backend" explicitly.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/blairanderson/rizzformsRizzForms — Form Backend Skill
Create forms that collect submissions and deliver them via webhook — no server code required. RizzForms handles storage, spam filtering, and delivery.
Bundled CLI
This skill includes a CLI at scripts/rizzforms. Use it instead of writing raw
curl commands — it handles authentication, pretty-prints JSON, and has commands
for every API operation.
# Make sure it's executable
chmod +x <skill-path>/scripts/rizzforms
# Set the API key (or run `rizzforms config` interactively)
export RIZZFORMS_API_KEY="frk_..."
# Now use it
<skill-path>/scripts/rizzforms forms
<skill-path>/scripts/rizzforms forms:create "Contact Form"
Run <skill-path>/scripts/rizzforms help for the full command list.
Prerequisites
You need a RizzForms API key with the admin role (prefix frk_).
Check for an API key: Look for RIZZFORMS_API_KEY in the environment or
~/.config/rizzforms/config.
If no API key exists:
- Sign up at https://forms.rizzness.com/signup
- Go to Account Settings > API Keys > Create API Key (select Admin role)
- Set it:
export RIZZFORMS_API_KEY="frk_..."
Important: Two Subdomains
RizzForms uses two subdomains — using the wrong one is a common mistake:
| Subdomain | Purpose |
|---|---|
forms.rizzness.com | Form submissions only (/f/ and /json/ routes) |
www.rizzness.com | API, dashboard, docs (/api/ routes) |
HTML form action and JSON submission URLs use forms.rizzness.com.
API management calls use www.rizzness.com.
The CLI handles this automatically.
Workflow
Step 1: Create a form
<skill-path>/scripts/rizzforms forms:create "Contact Form"
The response includes endpoint_token, submission_url, json_url,
embed_html, and examples with ready-to-use curl commands.
Save the endpoint_token — you need it for every subsequent step.
Step 2: Configure a webhook (optional)
If the user wants submissions delivered to an external URL:
<skill-path>/scripts/rizzforms plugins:create <endpoint_token> "https://their-server.com/webhook"
Requirements:
- URL must use HTTPS
- URL must not resolve to a private/reserved IP
- Save the
signing_secretfrom the response — it's shown only once
The webhook receives a JSON POST on each submission:
{
"id": 12345,
"created_at": "2026-03-22T12:00:00Z",
"form_id": "abc123",
"form_name": "Contact Form",
"ip": "203.0.113.42",
"user_agent": "Mozilla/5.0...",
"referrer": "https://yoursite.com/contact",
"data": {
"name": "Jane Doe",
"email": "[email protected]",
"message": "Hello!"
}
}
Each webhook includes an X-RizzForms-Signature header (HMAC-SHA256 of the
body using the signing secret). See references/api.md for verification
examples in Ruby, Node.js, and Python.
Step 3: Test the pipeline
<skill-path>/scripts/rizzforms test <endpoint_token>
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-blairanderson-rizzforms": {
"enabled": true,
"auto_update": true
}
}
}