Skip to content

Formpik docs

The AI-first form platform for everything your forms need

Formpik collects submissions from any website, drafts forms with AI, and runs every submission through a visual flow that checks it, sorts it and delivers it to the right person.

On this page you will learn

  • Who Formpik is for and the problem it solves
  • The path every submission takes, from your website to your team
  • What you can build with forms, flows and destinations
  • What a typical first week with Formpik looks like
  • Where to go next in these docs

What Formpik does

A form on a website is only the start. Someone has to read each submission, decide who it is for, reply, and copy it into the tools the team uses. Formpik does that part for you, and AI does the reading: it summarizes long messages, sorts submissions into categories and pulls out the details that matter.

  • Keep the forms you already have on Webflow, Framer, WordPress, Wix, Squarespace or plain HTML, or describe a new one and let AI draft it.
  • Choose from 26 field types, from ratings and opinion scales to multi-select, country and file uploads.
  • Draw a flow once: validate, filter spam, ask AI, route by any answer, wait, and deliver to email, Slack, Teams, Discord or a webhook.
  • See every submission, and every step every flow took, in one inbox. Export it, or read it from your own code with the API.

Who it is for

Formpik fits any team that gets forms from a website and has to act on them. You do not need to write code to use it: if you can paste a snippet into your site builder, you can connect a form.

You areWhat Formpik does for you
An agency or freelancerCollect quote requests from several client sites in one workspace, send each one to the right person by service or budget, and reply to the sender automatically.
A SaaS or product teamTurn a support or contact form into sorted messages: AI summarizes each one, billing questions go to one Slack channel, bug reports to another, sales leads to the CRM by webhook.
A marketing teamRun sign-up, event and newsletter forms on any page builder, keep spam out, and export the list when you need it.
A developerSkip building a backend for forms. Post JSON or a form to one endpoint, and read submissions back with the API.

How a submission travels

  1. 01WebsiteYour form, on any site builder or your own code.
  2. 02SourceThe endpoint address your form posts to.
  3. 03FormThe fields, and the rules for spam and limits.
  4. 04FlowsValidate, ask AI, route, wait.
  5. 05DestinationsEmail, Slack, Teams, Discord, webhooks.
  6. 06InboxEvery answer and every step, kept for you.
The colors match the flow editor: cobalt for the trigger, orange for logic, teal for actions.

Your website posts to a source, an endpoint address that belongs to one form. The form describes the fields and decides which submissions it takes. Every live flow of that form then runs for the submission, and its steps deliver to destinations. The submission and the history of every run are kept in the inbox, so you can always see what happened and why.

Formpik answers your website first and runs the flows right after, so visitors never wait for your emails or webhooks. Read the whole journey, step by step, in How Formpik works.

An example

A design agency has a quote form on its Webflow site with a service dropdown and a budget field. In Formpik it builds one flow:

  1. Validate checks the answers and holds back spam, such as throwaway email addresses.
  2. Ask AI writes a two-line summary of the project description.
  3. Route by answer sends website projects to the web team's Slack channel and branding projects to the design lead by email.
  4. Reply to sender thanks the visitor and says when they will hear back.

The agency never changes its website again: when the team changes, it edits the flow.

Your first week

Most teams get going in this order. You can do the first three steps in one sitting.

  1. 01

    Day one: one form, one website

    Sign in, create a form (with AI or from a template), and connect the website it lives on. The overview shows a short checklist that walks you to your first submission. Follow the Quick start.
  2. 02

    Day one: a first flow

    Start from the Notify the team or Route by answer template, test it with sample answers, and go live.
  3. 03

    Day two or three: invite the team

    Invite the people who handle submissions as editors, and the people who only read them as viewers. See Workspaces and team.
  4. 04

    During the week: connect your tools

    Add a Slack, Teams or Discord channel, or a webhook into your CRM, and swap the email steps for them where it helps. See Destinations.
  5. 05

    End of the week: tune it

    Read the inbox. Fix anything under Needs attention, review what was held as spam, and add allowed websites or a bot check if spam gets through.

Where to go next