AFI AFI

Everest Forms

Estimated reading: 2 minutes Updated August 1, 2026

Everest Forms is a free WordPress form builder by WPEverest with a drag-and-drop builder and conditional logic. Advanced Form Integration captures every Everest Forms submission and routes the data to any of 200+ destinations.

What you’ll need

  • The Everest Forms plugin (free or Pro) installed and activated.
  • The Advanced Form Integration plugin installed and activated.
  • An Everest Forms form built and published.

Supported form fields

Field type Supported Output format / notes
Single line text Yes Same as input
Email Yes Same as input
Number Yes Same as input
Phone Yes Same as input
URL Yes Same as input
Textarea Yes Same as input
Date / Time Yes YYYY-MM-DD, HH:MM
Select Yes The selected option
Radio Yes The selected option
Checkbox Yes Comma-separated selected values
Hidden Yes Same as the hidden value
File upload Yes Comma-separated public URL(s)
Address Yes Each sub-field separately
Name Yes First/middle/last separately
Rating Yes Numeric value

Create the integration

  1. Go to WP Admin → AFI → Add New.
  2. Enter an Integration Title.
  3. In Trigger → Form/Data Provider, select Everest Forms.
  4. In Form/Task Name, choose the form to listen on.
  5. In Action → Platform, pick the destination and complete the field mapping.
  6. Optional: configure Conditional Logic.
  7. Click Save Integration.

Screenshot: AFI Add New screen with Everest Forms selected as the Form Provider

Conditional logic example

Goal: when an inquiry form’s Budget field exceeds $5,000, route to the senior sales rep’s HubSpot pipeline.

Create the HubSpot integration. Open the Conditional Logic panel, add a condition with the budget field, Greater Than, value 5000. Smaller-budget inquiries flow to the standard self-serve pipeline.

Troubleshooting

Form not appearing in the Form/Task Name dropdown

Everest Forms registers a form on first publish. Re-save the form, then reload the AFI integration screen.

Multi-step forms

For multi-step Everest Forms, AFI fires after the final step submits. Earlier steps don’t fire individual events.

Related docs