With the gwp_word_count merge tag modifier for Gravity Forms it is possible to use the word count value of a text field in a formula. This way you can create a flexible Pay per Word calculation based on the amount of words in a text field.
The gwp_word_count modifier will become available after installing the GravityWP – Advanced Merge Tags Add-On.
In this tutorial we will build a pay per word form for a news paper which sells text ads, with a base price of $25,- and $0.75 per word. Here is a step by step walkthrough:
Step 1: Create a new form with 3 fields:
- One Paragraph text field
- Two Number fields
Step 2: Assign the following labels to each field:
- Advertisement Text
- Number of words
- Total Price
Step 3: Set up the word counter
Select the ‘Number of words’ field and tick the ‘Enable Calculation’ option like so:
A formula field appears. Here we can enter merge tags and basic arithmetic operators to create calculations. The merge tags are the variables which represent a field value. For example:
{Advertisement Text:1}Normally it would make no sense to add the merge tag of a text field here, as you can’t calculate with non-numeric values. That’s why we also add a merge tag modifier to the merge tag, in this case the ‘gwp_word_count’ modifier:
{Advertisement Text:1:gwp_word_count}This modifier ensures the merge tag does not return text, but the number of words instead. This advanced merge tag modifier is only available if you have the Advanced Merge Tags addon installed and active.
Now you have a field word count itself ready. Now we will need to address the actual pay per word calculation.
Step 4: calculate the price based on the amount of words
For this step, we edit the Number field we created with the ‘Total Price’ label. Instead of the default format (9,999.99), we select the Currency format. Also, we enable the calculation for this field.
In this example, we will use the number 25 as the starting price. You can replace this number with any value of your choice or remove it entirely. Add a plus sign (+) after the number to indicate that it will be added to the price.
The next step is to include the merge tag for the words. To do this, click on “Insert Merge Tag” and select the name of the previous number field that we used to calculate the word count.
Next, we will use 0.75 for the price per word. After the merge tag, type “* 0.75” to indicate that each word should be multiplied by 0.75 and added to the product price. This means that each word adds $0.75 to the price. Make sure to use a dot (.) as the decimal separator, not a comma. The settings should look like this:
Now we are ready to go. Save your form and try it out.
Read tutorials about
How to Replace Zapier with n8n (Using the GravityWP n8n Connector)
Tired of burning Zapier tasks on every Gravity Forms submission? This guide shows you how to replace Zapier with n8n using the GravityWP n8n Connector. You’ll learn how to move an existing Zap step-by-step into n8n, cut automation costs, and keep full control over where your data lives.
n8n vs Zapier: Which Automation Tool Actually Fits Your Work?
Trying to decide between n8n vs Zapier? This article breaks down pricing, hosting, integrations, AI features, and where self-hosted n8n on a cheap VPS can beat Zapier’s task-based plans. You’ll also see how Gravity Forms users can plug in the GravityWP n8n Connector and move key workflows off Zapier without rebuilding their forms.
Cloudflare Tunnel + n8n: Expose Local n8n for Webhook Testing (Dev Only)
This guide shows how to use Cloudflare Tunnel Quick Tunnels to put a local n8n instance on the internet for real webhook testing. It’s a dev-only recipe that lets tools like GravityWP’s n8n Connector call your local n8n over HTTPS, without renting a VPS or opening ports.
Self-Host n8n with Docker on a VPS
Learn how to self-host n8n with Docker on a VPS using a production-ready setup. This step-by-step guide walks you through configuring Docker Compose, Postgres, HTTPS, and WEBHOOK_URL so you can run reliable, secure n8n workflows on your own server.
