Resources · Make integration

WS Form Make integrationAutomate WS Form with Make.

Every form your WordPress site collects can start an automation. The WS Form Make integration gives you 2 modules: one trigger that picks up new submissions and one API call for the rest. This page shows how to link your account and build a first working scenario.

Try the WS Form integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WS Form Make integration do for you?

The integration lets Make read what people submit through your WS Form forms and pass each entry to the next step of an automation, with no code. In Make, that automation is called a scenario: a chain of modules, each one a brick that watches, acts or searches in one app.

Leads reach the right tool on their own. Watch Submissions picks up each new entry of a contact form, and the next module of the scenario can hand it to any other app you use in Make. Nobody copies rows out of the WordPress dashboard anymore.

Registrations get processed as they come. An event sign-up form on your site feeds the same trigger, and each submission becomes one bundle, meaning one item passed from module to module. A bundle holds the answers of one person, so every registration is handled separately.

Anything outside the trigger stays reachable. Make an API Call talks to the WS Form API with the connection you already set up, which covers requests that the listed module does not.

Know the boundary before you start. The catalog is small, with a single scheduled trigger and the API module, and the setup needs WS Form PRO with its Make add-on. If you are also looking at n8n, read n8n vs Make. For a wider look at the platform, the Make review is a good start, and Make pricing explains what each plan allows.

Connect

How do you connect WS Form to Make?

  1. 01

    Prepare WS Form on WordPress

    Your site needs WS Form PRO with the Make add-on installed and activated, plus a published form that has received at least one submission. That first entry gives Make something to read when you test.

  2. 02

    Copy the API URL and key

    In the WordPress admin menu, click WS Form, then Settings, then the Make tab at the top. Copy the API URL and the API key shown on that page and keep them at hand.

  3. 03

    Create the connection in Make

    Add a WS Form module to your scenario and click Create a connection. The Connection name field is optional. Paste the credentials you copied, save, and every WS Form module can reuse this connection.

First scenario

Your first scenario with WS Form

GoalWhen someone submits a WS Form form, Make picks up the entry and passes its answers to a WS Form API request.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the editor to add the very first module.

  2. 02

    Add Watch Submissions

    Search for WS Form, choose Watch Submissions and select your connection. Once the connection works, Make lists the forms it can read, so you only pick the one you want to follow.

  3. 03

    Chain Make an API Call

    Click the + to the right of the trigger and add Make an API Call from WS Form. Map answers from the submission into the request, following the WS Form API documentation for the endpoint.

  4. 04

    Test with Run once

    Click Run once, then send a new entry through the form on your site. Open each module afterwards to read the bundle it received and check that the answers landed where you expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks for entries. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Triggers

What starts a WS Form scenario

1 module starts a scenario when something happens in WS Form. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by WS Form as soon as it happens.

WS Form1Watch Submissions

Watch Submissions

Scheduled trigger

In Make“Triggers when a new submission occurs for a form.”

Each time a visitor completes one of your WS Form forms, this trigger hands the entry to Make so the rest of the scenario can use every answer. One submission turns into one bundle, and each bundle runs through the following modules on its own.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule and collects the entries that arrived since the previous check.
When to use it
a quote request or event registration form whose answers must end up in another tool without anyone retyping them.
Watch out
the form must be published and have at least one submission before you set up the module, otherwise there is nothing to pick from or test with.
Modules

What else WS Form can do in Make

WS Form gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

WS Form1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module gives you access to the WS Form API beyond the single trigger, reusing the same connection, so you never paste the key twice. You decide which endpoint to call and what to send.

When to use it
you need something from WS Form that Watch Submissions does not deliver, and the vendor's API documentation describes the request.
Watch out
each call counts as one operation on your Make plan, like any other module, so check with Run once that it sends what you expect.
Need help

Need help automating WS Form with Make?

A person reads every message.

FAQ

WS Form and Make: common questions

01Is the WS Form Make integration free?
Yes, on the Make side. WS Form is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and stops each run after 5 minutes. Files are capped at 5 MB, with 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. On the WS Form side, the Make add-on requires WS Form PRO, so check the vendor's own pricing page for that part.
02What do you need to connect WS Form to Make?
You need WS Form PRO with the Make add-on installed and activated, a published form that already has at least one submission, and the API URL and API key. Both values sit in WordPress under WS Form, then Settings, then the Make tab. In Make, click Create a connection on any WS Form module, give it a name if you like, and paste the two values. The same connection then serves every WS Form module in your scenarios.
03Does the WS Form trigger fire instantly?
No. Watch Submissions is a scheduled trigger: Make checks WS Form on the scenario's schedule and processes the entries received since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. For most lead and registration forms, that pace is enough, and each new entry still becomes its own bundle in the scenario.
04What if the WS Form module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the WS Form API with the connection you already created, so there is nothing new to authorize. You pick the endpoint and the data from the vendor's API documentation. Keep in mind that the Make documentation for this app carries a warning that part of its content was generated with AI, so confirm important details with WS Form directly before relying on them.
05Should you use Make or n8n for WS Form?
It depends on the tool your team already runs. In Make, WS Form offers the Watch Submissions trigger and the Make an API Call module, both working through one connection with your API URL and key. On the n8n side, check whether a WS Form node exists before you choose. The practical question is where the rest of your workflows live, since keeping form automations next to them makes them easier to follow and maintain for everyone involved.
Same platform

Other docs you might need on this stack.

Browse all integrations