# Pabbly Connect Workflow Builder MCP: Setup & Demo with Claude’s Free Plan

%[https://youtu.be/xe71rXSfawI]

What if you could describe an automation to Claude and have it build the workflow inside your Pabbly Connect account?

Choose the apps. Add the steps. Map the fields. Test the result.

That is what I wanted to explore with **Pabbly Connect’s Workflow Builder MCP**.

Hi, I’m Fagun Shah from [Integration Lab](https://www.integrationlab.in/). In this tutorial, I’ll show you how I connected Pabbly Connect to Claude and built an automation that sends form submissions to GoHighLevel.

The part I cared about most was **whether AI could handle the actual data mapping**, including a custom field. A workflow structure is useful, but the automation only becomes valuable when the right information reaches the right place.

For this demo, I used **Claude’s free plan**.

## What is Pabbly Connect Workflow Builder MCP?

MCP stands for **Model Context Protocol**. It gives AI assistants a standard way to connect to tools and take actions in other software.

For this tutorial, think of MCP as the connection between Claude and your Pabbly Connect account.

You describe the automation in a conversation. Claude uses the tools exposed by Pabbly’s Workflow Builder MCP to work on the workflow and guide you through the setup.

You still authorize your accounts and provide details the AI cannot know. In my demo, that included connecting GoHighLevel and adding a webhook to my form.

### How is it different from Pabbly’s other MCP features?

Pabbly has different MCP features for different jobs:

| MCP feature | What it is for |
| --- | --- |
| **Workflow Builder MCP** | Building and configuring automation workflows between apps. |
| **Integration Builder MCP** | Building custom app integrations, including their actions and triggers. |

If your goal is to connect a form to a CRM, you want **Workflow Builder MCP**.

The [Integration Builder connector](https://docs.pabbly.com/pabbly/doc/pabbly-connect-test-docs-kamal-bce0j) serves a different purpose: creating or extending an app integration.

## The demo: Send form inquiries to GoHighLevel

Here is the automation we will build:

**Pabbly Form Builder → Pabbly Connect → GoHighLevel**

My form collects four pieces of information:

- First name
- Last name
- Email address
- Inquiry message

When someone submits the form, their details should reach GoHighLevel, with the message saved in an existing contact custom field called **Inquiry**.

Inside Pabbly Connect, the integration used in my demo was **LeadConnector V2**. Claude recognized GoHighLevel and selected that integration without me having to specify the Pabbly app name.

## What you need before starting

Have these ready:

- A [Pabbly Connect account](https://connect.pabbly.com/).
- A [Claude account](https://claude.ai/).
- A Pabbly Form Builder form with the fields listed above.
- Access to the GoHighLevel account or sub-account you want to use.
- A contact custom field named **Inquiry** in GoHighLevel.

I created the form and the custom field before recording the demo.

**Can you use Claude’s free plan?** Yes—I used it for this walkthrough. Claude’s current documentation also lists remote custom connectors on the Free plan, with a limit of **one custom connector**. Normal usage limits still apply. [Claude Help Center](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities?utm_source=chatgpt.com)

This tutorial covers the Claude setup I tested. The Pabbly screen in my demo also offered ChatGPT, but I did not test that route or confirm its plan requirements.

## Step 1: Open the Workflow Builder MCP setup in Pabbly Connect

Log in to [Pabbly Connect](https://connect.pabbly.com/) and click **Create Workflow**.

In my demo, the screen included an option to **build workflows with Claude or ChatGPT**. Open that option and select **Claude**.

Copy the MCP server URL shown in that setup screen.

**Use the URL provided for Workflow Builder.** Pabbly’s Integration Builder and workflow action MCP features have different purposes, so their setup instructions should not be substituted here.

Button labels may change as the interface develops; these steps follow the flow shown in my recording.

## Step 2: Add Pabbly Connect as a custom connector in Claude

Open Claude’s connector settings.

In the interface shown in my demo, I selected **Add → Custom**. Claude’s current help documentation describes this under **Customize → Connectors**, with a custom web connector option. [Claude Help Center](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities?utm_source=chatgpt.com)

Then:

1. Enter a name, such as **Pabbly Connect Workflow Builder**.
2. Paste the MCP server URL copied from Pabbly.
3. Click **Continue**.
4. Review the detected authentication settings.
5. Finish adding the connector.

The name is only a label to help you recognize the connection. You do not need to use the exact product name.

In my demo, the detected settings worked without changes.

## Step 3: Authorize your Pabbly Connect account

After adding the connector, click **Connect**.

A Pabbly authorization page opens. Sign in if needed, check the account, and click **Allow**.

Return to Claude and confirm that the connector is connected and available in your conversation.

Claude may ask for permission when it uses tools. In my demo, I chose **Always allow** for the relevant tools to reduce repeated prompts. You can also review requests individually.

The connection is now ready for the workflow-building conversation.

## Step 4: Describe the automation

My initial request was simple:

> I want a Pabbly workflow which connects my Pabbly form to GHL.

Claude searched the app catalog, identified LeadConnector V2, and created the initial workflow structure.

**That first structure appeared in roughly 20–25 seconds in my demo.** The workflow still needed account authorization, sample data, field mapping and testing.

For a clearer starting request, you can use:

> Create a Pabbly Connect workflow that sends new Pabbly Form Builder submissions to GoHighLevel through LeadConnector V2, maps first name, last name and email dynamically, and saves the inquiry message in my existing Inquiry contact custom field; guide me through authorization and testing, and keep the workflow off until I review it.

The more clearly you describe the destination and field requirements, the less the AI has to infer.

## Step 5: Connect GoHighLevel

Claude provided a connection link so I could authorize my GoHighLevel account.

Open the link, sign in if required, select the appropriate account or location when prompted, and grant access.

Then return to Claude and tell it that the connection is complete.

This step matters: **connecting Claude to Pabbly does not automatically connect every app your workflow uses**. The destination app still needs its own authorized connection.

## Step 6: Add the webhook to your form

Next, Claude provided the workflow’s trigger webhook URL and asked me to add it to my form.

In Pabbly Form Builder:

1. Open your form.
2. Go to **Integrations**.
3. Click **Add Webhook**.
4. Paste the webhook URL supplied for this workflow.
5. Save the integration.

Tell Claude when you have saved it.

The webhook is the delivery address your form uses to send each submission to Pabbly Connect.

## Step 7: Capture a sample submission

Before Claude can map the fields, it needs to see what the form sends.

Follow its instructions to prepare the trigger to capture data, then submit the form with all four fields filled in.

**Wait until the trigger is ready before submitting.**

I had to submit the form again during the demo because I initially misunderstood the capture instructions. If the sample does not appear, check that capture is active, then send another submission.

Once the data arrives, Claude can identify the form fields and use them in the destination step.

## Step 8: Map the contact fields and the Inquiry custom field

The intended mapping is:

| Form field | GoHighLevel destination |
| --- | --- |
| First name | First Name |
| Last name | Last Name |
| Email address | Email |
| Inquiry message | Inquiry contact custom field |

Claude mapped the standard contact fields. For the message, I clarified:

> I have a custom field called Inquiry.

That gave Claude the destination it needed to complete the custom field mapping.

### What does dynamic mapping mean?

Dynamic mapping tells the workflow to use the value from **each incoming submission**.

For example, mapping the form’s Email field means every new contact receives that submitter’s email address. Entering the sample email as fixed text would reuse the same address.

When I opened the workflow in Pabbly Connect, I could see dynamic mappings in the action step. The Inquiry value also reached the correct custom field during testing.

**This was the most important result of the demo.**

## Step 9: Open the workflow and review it

You can ask Claude:

> Give me the workflow link.

Open the link to inspect what it built.

Check the trigger response, destination connection, action settings and field mappings. Confirm that the message points to **Inquiry**, rather than an unrelated contact field.

In my demo, Claude also added notes to the workflow, providing some documentation alongside the setup.

## Step 10: Run an action test and resolve validation errors

Ask Claude to test the destination action.

My demo encountered this error:

> Contact with DND must be a boolean value.

**DND** means **Do Not Disturb**. A boolean field expects a value such as `true` or `false`.

Claude reported that its attempt to skip the field had been rejected. I agreed to set it to `false`, which matched the setting I wanted for this demo, and the test then worked.

Review that setting for your own workflow: DND affects contact communication preferences.

After the successful test, I refreshed GoHighLevel and checked the contact. The standard details and the **Inquiry custom field value** were present.

## Step 11: Enable the workflow and test a fresh submission

An action test checks the destination step. A fresh form submission checks the complete path.

After reviewing the workflow, confirm that it is **ON** before running the live test.

Submit the form again using a different valid email address and a recognizable inquiry message. Then open GoHighLevel and verify:

- The new contact appears.
- The name and email are correct.
- The Inquiry field contains the new message.

During my demo, the form rejected one invalid email address. After correcting it and submitting again, the second contact appeared with the expected inquiry.

That confirmed the automation worked beyond the captured sample.

## Step 12: Check the workflow history

Open the workflow’s **Task History** in Pabbly Connect.

The live submission appeared there with a task history ID, just like a manually created workflow.

Once configured and enabled, Pabbly Connect runs the automation. You do not need to keep the Claude conversation open for each new submission.

## What still needs your input?

AI handled much of the workflow configuration in this demo, while I still needed to:

- Authorize Pabbly Connect and GoHighLevel.
- Add the webhook to the form.
- Send sample data at the right time.
- Clarify the custom field name.
- Confirm a setting when validation failed.
- Review and test the completed automation.

For this use case, I did not need to write API requests or code. Understanding the outcome and checking the result remained essential.

## What about AI access to task history?

During the recording, I mentioned planned support for AI access to workflow history.

**That was a future capability discussed in the demo, not something demonstrated here.** Check Pabbly’s current release notes before relying on it.

The test covered workflow creation, connection setup, field mapping, a validation fix and successful execution.

## My experience

For me, this is one of Pabbly Connect’s most useful updates for people who know what they want to automate but find the setup difficult.

I could describe the workflow in ordinary language, follow the connection prompts, and let Claude handle much of the configuration—including a custom field.

The useful part is how far the conversation carried the setup: from an idea to a workflow that passed a live form submission into GoHighLevel.

If you try Pabbly Connect Workflow Builder MCP, let me know what you build and where you get stuck.

For help with more complex workflows for your business, reach out through [Integration Lab](https://www.integrationlab.in/).