Static Forms for agencies

What the Agency plan includes

• 30,000 submissions per month. One allowance for the whole workspace, shared by every form. Opt-in overage is $1.00 per 1,000 extra submissions, billed monthly; it is off by default.
• Unlimited forms. One form per client site, or several per site, each with its own API key.
• Unlimited team members. Invite colleagues with admin access to every form, or a client or contractor with access to a single form.
• Lead management for 3 people. Track selected enquiries in a pipeline with assignments, private team notes and in-app follow-ups. 3 CRM users are included, counting the owner; extra CRM users cost $4 a month or $24 a year each, matching your billing cycle.
• 10 GB file storage. For file uploads across all forms. Files are attached to the notification email and stored privately for download from the Inbox.
• 25 form rules per form. Route, redirect or quarantine submissions on field values, with country, time of day, UTM, attachment and regex conditions.
• 25 verified recipient addresses. A workspace pool of confirmed addresses that form rules can route to, so a rule can only send to an inbox someone has confirmed.

It also has everything in Pro: file uploads, webhooks, Google Sheets, Notion, Airtable, Mailchimp and Zapier, custom email domains and removal of Static Forms branding. The pricing page compares every plan.

Setting up a client site

1. 1. Create a form for the client site

   In the Forms list, add a form named after the client or the site. Its API key is on the form's General tab.

2. 2. Add the form to the site

   Paste a plain HTML form that posts to the endpoint with the API key in a hidden field. It works on static sites, site builders and framework apps, with no server code on the client's hosting.

   contact.htmlCopy

   <form action="https://api.staticforms.dev/submit" method="POST">
     <!-- The API key from this client's form, on its General tab -->
     <input type="hidden" name="apiKey" value="CLIENT_FORM_API_KEY">
     <!-- Send visitors to a thank-you page on the client's site -->
     <input type="hidden" name="redirectTo" value="https://client.example/thanks">
   
     <label for="name">Name</label>
     <input type="text" id="name" name="name" required>
   
     <label for="email">Email</label>
     <input type="email" id="email" name="email" required>
   
     <label for="message">Message</label>
     <textarea id="message" name="message" required></textarea>
   
     <button type="submit">Send</button>
   </form>

3. 3. Lock it to the client's domain

   On the Security tab, turn on domain restriction and list the client's domains, so the form rejects submissions sent from other websites, and pick a captcha for that form. Set its spam level on the Spam filter tab.

4. 4. Send submissions where the client works

   On the Delivery tab, set the client's address as the recipient; the client confirms it from an email link before submissions go there. CC up to 5 more verified addresses (each copy counts toward the monthly allowance), and add a webhook, Google Sheets or a Slack channel if they use one.

5. 5. Give the client access to their form only

   From Workspace, Team, invite the client with access to that one form. They see its submissions and settings, not your other clients'.

The form posts to https://api.staticforms.dev/submit. Platform guides: plain HTML, WordPress, Webflow and Next.js. Team access levels are in the Team docs.

Settings that belong to each form

Each form keeps its own settings, so changing one client's setup leaves the others as they were. Team, billing and the verified-recipient pool are set once for the workspace, and sending domains are verified there once, then picked per form.

Redirect and reply-to are set per form with the hidden redirectTo and replyTo fields in the form's HTML (see the API reference). The notification subject template is on the Branding tab, and Rules can override the subject, reply-to and redirect for matching submissions.

The full map is in per-form vs workspace settings.

FAQ