Webhook Integration Guide

Integrations

Suggested articles

? Prerequisites

  • WordPress Admin Access

  • Fluent Forms plugin installed

  • WP Automator plugin installed (Free or Pro)

  • A destination webhook endpoint (e.g., your CRM or internal API)

? Step 1: Access Integrations

  • Navigate to the left sidebar

  • Click Integrations

  • Scroll down to Prospects Leads section

  • Click the Webhook card

  • Copy the webhook Url ( to be used in the coming step )

? Step 2: Create a Contact Form in Fluent Forms

  1. Go to Fluent Forms > Forms > New Form.

  2. Add the following fields:

    • First Name (required)

    • Last Name (required)

    • Email (required)

    • Phone (required)

    • Subject / Message / Remarks (optional)

    • Source (optional — e.g., “Website Contact Form”)

  3. For each field, click it and go to Input Customization > Advanced Options:
    Set the Name Attributes as follows:

    • first_name

    • surname

    • email

    • phone

    • source

    • remarks

Note: first_name, surname, email, and phone are required fields for successful webhook submission.

⚙️ Step 3: Set Up Automation with WP Automator

  • Navigate to Automator > Add New Recipe.

  • Name your recipe (e.g., "Webhook – New Lead").

  • Under Trigger, choose:

    • Fluent Forms

    • Form is submitted

    • Select your Contact Form Demo

  • Under Actions:

    • Select Webhooks → Send data to a webhook

    • Paste the copied Webhook URL from Step 1

⚠️ Important Settings:

Request Method:
  • Change to GET

Headers:

  • Add:

    • Name: Accept

    • Value: application/json

Body (Payload):

Under “Body”, map your Fluent Form fields to these keys:

KeyTypeValue (Token from Form)
first_nameTextFirst Name
surnameTextLast Name
emailTextEmail
phoneTextPhone
sourceTextSource
remarksTextSubject and/or School (if any)
 

? Combine Subject and School into remarks if both are used.

✅ Step 4: Save and Go Live

  • Click Save for the action and recipe.

  • Toggle the Live switch on the top-right of the recipe.

  • Submit a test entry using the Contact Form.

  • Make sure To-do the mapping correctly
  • After submitting the form, You should be able to check the entry record in Prospects in the dashboard.

? Step 5: Monitor & Troubleshoot

  • Go to Automator > Recipes > View Logs.

  • You’ll see “Completed Runs” with status per entry.

  • Check your receiving endpoint (e.g., CRM) to confirm data is coming through.

  • Make sure the Recipe status is Live. ( go to recipe and turn on the button)

? Sample Payload Sent json Copy Edit

{
"first_name": "John",
"surname": "Doe",
"email": "john.doe@example.com",
"phone": "+1234567890",
"source": "Website Contact Form",
"remarks": "Interested in Math - Greenwood High School"
}

?️ Troubleshooting Guide

Having issues with the webhook? Here are common problems and solutions:

 
ProblemCauseSolution
No data receivedUsing GET methodSwitch method to POST in Webhook Action
Only partial data receivedMissing form field mappingCheck field “Name Attributes” in Fluent Forms match webhook keys (e.g., first_name, surname)
Webhook failed in logsInvalid JSON or field missingEnsure all required fields are filled: First Name, Last Name, Email, Phone
No entry in logsForm not triggering the recipeVerify the correct form is selected in the trigger and that the recipe is Live
500/Internal Server ErrorServer rejected the requestConfirm the receiving server supports application/json and accepts POST with body
Combined field not clearRemarks field includes multiple tokensFormat Subject + School clearly (e.g., “Subject: Math

❓ Need Help?

  • Check Automator > View Logs to see submission status

  • Use a tool like Webhook.site to test your payload structure

  • Contact our support team with logs or screenshots for assistance

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article