Keep your forms moving.

Workspace and form limits

Your account plan applies to all workspaces you own. Joining someone else’s workspace does not use your owned-workspace allowance or change their plan. Suspended workspaces still count as owned.

Draft and paused forms count toward form capacity. Archived forms do not; restoring one requires an available slot. Projects and sources do not add form slots. At capacity, creation and restoration are blocked in both the app and API. If a plan change puts you over a workspace or form limit, you get seven days to choose active slots in Account capacity. Excess items then stop receiving submissions; existing data and draft settings remain available, and no records are deleted by the downgrade. Read the plan-change and gift policy.

Free is available now. Developer and Pro subscriptions are available now. Compare pricing and allowances →

Understand your allowance

Open Usage & plan to see your account’s owned-workspace capacity, the current workspace’s form slots, accepted submissions this month, attachment storage, and retention period. Capacity is available during setup; submission and storage usage require a verified account. Each workspace has a separate submission and storage allowance, shared across its forms.

A matching idempotent retry returns the original receipt without consuming another submission. Quarantined submissions count only when released into the inbox. Requests that exceed an allowance receive an error; they are not silently accepted.

Resume your form setup

Choose Create form in Forms to start the seven-step guide. Open a draft from the form list to continue at its next incomplete step. On an existing form, Open the guided setup & checklist lets you review the same settings in order.

Save this step and Save & continue store your choices and record that you reviewed them. Adding or removing a row does not save the step. A completed step becomes incomplete when the settings it covers change, including changes made in the standard editor. Review and save that step again; publishing remains a separate action.

Check connection readiness

Open the form’s guided setup and choose Review & publish for its saved-step checklist. The standard Overview also shows connection readiness. These prerequisites are shown separately:

Your own account verification is shown separately. An unverified teammate does not stop a form whose owner is verified, but that teammate must verify before publishing or accessing response data. If your email is already verified, an unpublished form needs publication rather than another verification email.

Publishing chooses the configuration for new submissions; it does not resume a paused form, restore an archived form, or enable a disabled source. The readiness checks cover setup. Submitted requests must still meet published rules, protection checks, and plan allowances.

Save and publish deliberately

In the guide, review Form details, Fields & behavior, Protection & files, Response delivery, and Website connection. Review & publish checks those saved choices alongside verification and connection availability. Confirm the checklist, then choose Publish form.

In Configuration, work through details, fields and validation, protection and attachments, and optional webhook actions. Save changes before publishing. Unsaved or invalid edits must be corrected and saved first; publishing uses the saved draft.

Versions identifies the currently published configuration. Copying an earlier version into your draft does not change the published version. Review and save any edits, then publish when ready. Source settings are separate: changes to a published form’s sources affect its endpoints immediately.

Confirm the connection

In Connect & test, use the endpoint and example for your selected connection. Website form accepts HTML or browser JavaScript; Trusted server requires the private source secret shown once when it is created. Changing a connection’s type replaces its endpoint and secret, so update your integration after confirming that change.

Send clearly labeled test data from your website or server, then choose Check for a response. The final step becomes complete when the required reviews are current, the saved configuration is published, the connection is ready, and an accepted response from the selected source has arrived using that published version after the connection was reviewed. A quarantined response does not satisfy this check. Changes to the connection or published version may require a fresh response.

The guide does not submit sample data automatically. A test uses your normal submission allowance and runs any configured, enabled webhooks. Check their outcomes separately in the saved response; confirming receipt does not confirm delivery to another system.

Follow a submission

An acceptance receipt confirms that Form Bastion stored your submission. Open it in the Inbox to review fields, attachments, and any connected actions. Form changes apply when you publish, and existing submissions keep the rules that were active when they arrived.

Understand delivery timing

Webhook actions run after a submission is saved. A queued action can appear alongside a saved submission while it waits for processing or a retry. Open Activity and choose Webhook deliveries to see recorded outcomes. Open the linked submission for attempt and response details.

If an action remains queued or a service is interrupted, check service status. Contact support with your form and action reference if you need help. The linked submission shows the recorded delivery details for each action.

Retry with care

Destinations configured for safe retries receive a stable idempotency key. An uncertain result from a destination without that protection is not automatically retried. Check the destination before deciding whether to repeat work. See webhook actions for delivery signatures and replay rules.

Keep what you need

Each submission has a retention expiry based on the plan in effect when it was accepted. Expired submissions, files, and action records are removed together through background cleanup. Export information you want to keep as CSV or JSON before it expires. Deleted or expired submissions cannot be recovered.

Plan for more volume

Review your submission and storage use before a large campaign. If your requirements exceed your current plan, talk to us about capacity.