PlanSo Forms is a form management and creation tool. It can be used directly or via wordpress plugin.

PlanSo Forms for WordPress

The newly redesigned Jotform lets you build forms faster than ever, with powerful widgets and a responsive editor that works offline—without even needing to sign up for an account.

Jotform

Gravity Forms is a premier WordPress plugin that makes it easy to create powerful forms on the fly.

Gravity Forms

Formidable Forms is a WordPress plugin that helps you create beautiful drag and drop forms with custom styling. You and your visitors can submit and edit entries and posts from the front-end of your site. When you have data, display it with graphs and custom views.

Formidable Forms

iFormBuilder is a universal, cloud based mobile data collection ("forms") platform with an emphasis on security on mobile devices, and collecting data with or without an Internet connection.

iFormBuilder

Ninja Forms is the easiest and most flexible WordPress Form builder.

Ninja Forms

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Interfaces

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given `{"contact": {"name": "Mike"}}`, add "contact" here to only return `{"name": "Mike"}`. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: `[{"id":1234},{"id":1235}]`

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the `id` key. If the `id` key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with `id` in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (`|`) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request `data` below will be overridden with the raw data from the previous step (you are still responsible for headers though, like `Content-Type`). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data `Content-Type`. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

Returns the raw response from the request, in the following keys: response, status, headers. Ignores `Unflatten`.

We recommend *not* putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. *Note:* If you specify nothing for this field, **we will automatically encode and include every field** from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the **Custom Request** action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to `multipart/form-data`, with the above payload type defining the sub content-type for the data being passed.

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Webhooks by Zapier

Manage your WordPress updates effortlessly with this workflow. Every time a new submission happens in your PlanSo Forms for WordPress, a corresponding update is created in Webhooks by Zapier instantly. This simplifies your content management process and eliminates the need for manual transfers, enhancing efficiency.

PlanSo Forms for WordPress + Webhooks by Zapier

Create posts with Webhooks by Zapier when new submissions occur in PlanSo Forms for WordPress

Supported triggers and actions

New Submission

Catch Hook

Custom Request

POST

Catch Raw Hook

Retrieve Poll

GET

PUT

About PlanSo Forms for WordPress

Related categories

Similar apps

Jotform

Gravity Forms

Formidable Forms

About Webhooks by Zapier

Related categories