TutorialGravity Forms monday.com Integration: Create New Items From Form Submissions

Do you want to send Gravity Forms submissions to monday.com without copying entries by hand?

In this tutorial, you will build a practical Gravity Forms monday.com integration using GravityWP API Connector. The setup connects WordPress, Gravity Forms, and monday.com through the monday.com API.

When someone submits a form on your WordPress site, the form data is sent to monday.com. A new item is then created on a monday.com board.

We tested this workflow with a simple project request form. The final setup created a new monday.com item. It also filled the mapped monday.com board columns, saved the returned monday.com item ID back to Gravity Forms, and stored the full API response in the Gravity Forms entry.

The workflow looks like this:

Gravity Forms submission
→ GravityWP API Connector
→ monday.com API
→ New monday.com item created
→ monday.com item ID saved back to Gravity Forms

monday.com’s platform API is GraphQL-based. API requests are sent as POST requests with a JSON body. The access token is sent in the Authorization header. monday.com also says GraphQL queries and mutations should be sent with the query key in the JSON body. See the monday.com API getting started guide.

What does this Gravity Forms and monday.com integration do?

This tutorial creates a real workflow between Gravity Forms and monday.com.

When a user submits the form, GravityWP API Connector sends the submitted form data to monday.com. monday.com then creates a new item on a board.

In our tested example, the form submission created a new item in a monday.com board called Project Requests.

The submitted values were saved into these monday.com columns:

• Requester Name
• Requester Email
• Department
• Request Type
• Priority
• Due Date
• Request Details

The setup also saved the returned monday.com item ID inside the Gravity Forms entry. This is useful because you can track which form entry created which monday.com item.

This tutorial focuses on creating a new monday.com item. It does not create a monday.com WorkForm, a CRM lead, or a multi-step automation. You can use the same idea for a monday.com CRM board, but this example is built around project requests.

What you need to integrate Gravity Forms with monday.com

Before you begin, make sure you have:

• A WordPress site
• Gravity Forms installed
• GravityWP API Connector installed
• A monday.com account
• A monday.com board
• A monday.com API token
• Access to edit a Gravity Form

You also need to copy IDs from monday.com and use Gravity Forms merge tags. We will explain where each value goes.

monday.com uses token-based authentication for API requests. The token should be passed in the Authorization header. You can learn more in the monday.com authentication documentation.

Step 1: Create a monday.com board for Gravity Forms submissions

First, create a board in monday.com.

For this tutorial, we used this board name:

Project Requests

This monday.com board will receive the Gravity Forms submissions.

Add these columns to the board:

The first column in a monday.com board is the item name. In this tutorial, we use the Gravity Forms Request Title field as the monday.com item name.

For the first setup, we recommend using mostly Text columns. Text columns are easier to test because they can accept simple text values. The Request Details column uses Long Text, so it needs a slightly different format in the API request.

monday.com’s API uses column_values to set board column values when creating or updating items. The column values are sent as a JSON-formatted string. You can read more in the monday.com items API documentation.

Step 2: Get your monday.com board ID and column IDs

Next, collect the IDs you need for the API request.

Get the monday.com board ID

Open your monday.com board and check the browser URL.

It may look like this:

https://yourcompany.monday.com/boards/5029849336

The number after /boards/ is the board ID.

In our test, the board ID was:

5029849336

Get the monday.com column IDs

To copy column IDs, enable Developer Mode in monday.com.

Go to:

Profile menu → monday.labs → Developer mode

After Developer Mode is enabled, open the menu for each column and copy the column ID.

In our tested board, we used these monday.com column IDs:

Requester Name: text_mm56sfch
Requester Email: text_mm56tvnp
Department: text_mm56ff2q
Request Type: text_mm563cy5
Priority: text_mm564cww
Due Date: text_mm563e1f
Request Details: long_text_mm56a766

Your IDs will be different. Do not copy these values unless you are working on the same test board.

Step 3: Set up Gravity Forms for the monday.com workflow

Now create the form in Gravity Forms.

In WordPress, go to:

Forms → New Form

Name the form:

Project Request Form

Add these fields:

For the Department dropdown, you can use:

• Marketing
• Sales
• Support
• Operations
• Development

For the Request Type dropdown, you can use:

• New Project
• Support Task
• Client Request
• Internal Task
• Onboarding

In Priority dropdown, you can use:

• Low
• Medium
• High
• Urgent

Set these two fields to Administrative visibility:

monday.com Item ID
monday.com Item Response

These fields are not for the person filling out the form. They store data from the monday.com API response inside the Gravity Forms entry.

Gravity Forms explains that Administrative visibility hides a field from the public form while keeping it available in the admin area. See the Gravity Forms common field settings documentation.

Step 4: Create the monday.com API connection in GravityWP API Connector

Now create the monday.com API connection in GravityWP API Connector.

Go to your API Connector settings and add a new API connection.

Use these settings:

Do not share your API token publicly. Paste it only inside your WordPress admin settings.

The endpoint will be added later in the feed as:

/v2

Together, the base URL and endpoint create the full monday.com API URL:

https://api.monday.com/v2

This keeps the API connection reusable. You can use the same API connection for other monday.com feeds later.

Step 5: Create the Gravity Forms to monday.com API Connector feed

Next, go to your form settings:

Project Request Form → Settings → API Connector

Create a new feed.

Use these settings:

In the Query String / Body Parameters section, add:

This is the key part. monday.com expects the GraphQL mutation to be sent inside a query value in the JSON body.

For the response mapping, use:

GravityWP API Connector can map JSON response paths into Gravity Forms fields. It can also store the raw response, which is useful for testing and troubleshooting. See the API Connector feed settings documentation.

Step 6: Add the monday.com create_item mutation

Now add the mutation that creates the monday.com item.

monday.com’s API supports creating items through the create_item mutation. The mutation can return fields such as the new item’s ID, name, and URL. You can learn more in the monday.com GraphQL overview.

Here is the final tested mutation from our setup:

mutation { create_item(board_id: 5029849336, item_name: "{Request Title:1}", column_values: "{\"text_mm56sfch\":\"{Requester name (First):3.3} {Requester name (Last):3.6}\",\"text_mm56tvnp\":\"{Requester Email:4}\",\"text_mm56ff2q\":\"{Department:5}\",\"text_mm563cy5\":\"{Request Type:6}\",\"text_mm564cww\":\"{Priority:7}\",\"text_mm563e1f\":\"{Due Date:8}\",\"long_text_mm56a766\":{\"text\":\"{Request Details:9}\"}}") { id name url } }

Paste this into the Value field for the query body parameter.

Then replace these values with your own:

1. 5029849336 → your monday.com board ID
2. text_mm56sfch → your Requester Name column ID
3. text_mm56tvnp → your Requester Email column ID
4. text_mm56ff2q → your Department column ID
5. text_mm563cy5 → your Request Type column ID
6. text_mm564cww → your Priority column ID
7. text_mm563e1f → your Due Date column ID
8. long_text_mm56a766 → your Request Details column ID

Also check your Gravity Forms merge tags. In our tested form, these were the field IDs:

Request Title: {Request Title:1}
Requester name: {Requester name (First):3.3} {Requester name (Last):3.6}
Requester Email: {Requester Email:4}
Department: {Department:5}
Request Type: {Request Type:6}
Priority: {Priority:7}
Due Date: {Due Date:8}
Request Details: {Request Details:9}

Your field IDs may be different. This can happen if you added, deleted, or recreated fields while building the form.

Step 7: Test the Gravity Forms to monday.com workflow

Now submit a test entry.

Use sample values like this:

After submitting the form, check your monday.com board.

You should see a new item with the submitted values.

In our test, monday.com created a new item with this item name:

Website landing page update

The row also included:

Requester Name: Jon Alexander Castillo
Requester Email: jonalexander@gravitywp.com
Department: Marketing
Request Type: Support Task
Priority: High
Due Date: 2026-07-30
Request Details: Please update the homepage hero section, contact form, and call-to-action button for the new campaign.

Then check the Gravity Forms entry.

In our test, Gravity Forms saved the returned monday.com item ID:

2779316794

It also saved the full monday.com response in the monday.com Item Response field.

That confirms the data transfer is working.

Why use Text columns first in this monday.com integration?

You may wonder why this tutorial uses Text columns for fields like Priority and Due Date.

The reason is simple. Different monday.com column types can need different value formats.

A Text column can use a simple value:

"text_mm56ff2q":"{Department:5}"

A Long Text column needs a different structure:

"long_text_mm56a766":{"text":"{Request Details:9}"}

This makes Text columns easier for your first Gravity Forms to monday.com setup.

After the basic integration works, you can test more advanced monday.com column types like Status, Date, Email, or People. Check monday.com’s API documentation for the correct value format before changing the mutation.

Troubleshooting Gravity Forms and monday.com API errors

If the integration does not work on the first try, check these common issues.

The monday.com item is not created

Check these settings:

• The monday.com API token is correct
• The API Key Parameter Name is Authorization
• The API Key Placement is Header
• The request method is POST
• The endpoint is /v2
• The body format is JSON body
• The body parameter key is query

If the API token is wrong, monday.com will reject the request.

The item is created, but the columns are empty

This usually means the basic create_item mutation worked, but the column_values part did not.

Check:

• The column IDs are correct
• The column_values string is included
• The monday.com board has those columns
• The Gravity Forms merge tags are correct

If a column ID is wrong, monday.com cannot place the value in that column.

The monday.com Item ID is not saved in Gravity Forms

Check the target field mapping.

Use:

Target field: monday.com Item ID
Response key: data/create_item/id

Also make sure the mutation returns id:

{ id name url }

If the response does not include id, API Connector cannot save it into the target field.

The Long Text field does not save correctly

For the Long Text column, use this format:

"long_text_column_id":{"text":"Your text here"}

In our test, this worked:

"long_text_mm56a766":{"text":"{Request Details:9}"}

The form works once, then fails after editing fields

If you edit your Gravity Forms fields, check your merge tags again.

Gravity Forms field IDs can change if fields are deleted and recreated. That means a merge tag like this:

{Requester Email:4}

may not match your current form anymore.

Use the merge tag picker in API Connector to confirm the correct field IDs.

When should you use a more advanced monday.com workflow?

This tutorial is best for a simple no-code workflow:

1. Create a new monday.com item from a Gravity Forms submission
2. Send basic form data to monday.com
3. Save the returned monday.com item ID
4. Reduce manual effort
5. Keep form entries connected to monday.com items

For more advanced workflows, you may need extra setup.

Examples include:

• Updating existing monday.com items
• Creating subitems
• Assigning people columns
• Using advanced Status or Date formatting
• Adding conditional routing
• Sending files
• Running multi-step workflows

For multi-step automation, you may want to use a tool like n8n with Gravity Forms. This can be useful when one API step depends on the result from a previous API step.

Conclusion

You now have a working Gravity Forms monday.com integration that creates a new monday.com item from a form submission.

The setup uses GravityWP API Connector, a monday.com API token, and the monday.com create_item mutation. It sends submitted form values to a monday.com board and saves the returned item ID back to the Gravity Forms entry.

This is useful when your team collects requests in WordPress but manages the work in monday.com. Instead of copying form entries by hand, each new form submission can become a new action item on your monday.com board.

FAQ about Gravity Forms and monday.com integration

Our Premium add-ons for Gravity Forms

List Dropdown

Add a Dropdown Select with choices to a column or multiple columns in a Gravity Forms List Field.

Advanced Merge Tags

This Gravity Forms Add-On adds extra Merge Tag modifiers (and a lot of power). From the most common used functions like capitalize and length to changing date formats.

Entry to Database

Integrates Gravity Forms with internal or external databases, offering flexible mapping of form fields to database columns and real-time synchronization between entries and database rows.

Field to Entries

Create entries based on Checkboxes & Multi Select choices & List Field rows.

See all add-ons

Read tutorials about

Gravity Forms monday.com Integration: Create New Items From Form Submissions

Learn how to connect Gravity Forms to monday.com without Zapier using GravityWP API Connector. This step-by-step tutorial shows how to create new monday.com items from form submissions and save the returned monday.com item ID back to Gravity Forms.

Gravity Forms Pipedrive Integration: Send Form Contacts to Pipedrive Without Zapier

Learn how to connect Gravity Forms to Pipedrive without Zapier using GravityWP API Connector. This step-by-step tutorial shows how to send form contacts, custom fields, and the returned Pipedrive Person ID directly from WordPress to Pipedrive CRM.

Show Previous Gravity Forms Submissions Using Advanced Merge Tags

This step-by-step tutorial shows how to use GravityWP Advanced Merge Tags to count previous Gravity Forms submissions and calculate total submitted value based on a matching email address.

Gravity Forms LeadConnector Integration with OAuth 2.0

This documentation-based tutorial explains how to connect Gravity Forms to LeadConnector/HighLevel with OAuth 2.0, search contacts by email, and map returned CRM values back into form fields using GravityWP API Connector.

See all tutorials