Integrations · Lead sources

WordPress forms into Tripdocks

Your website's enquiry form, feeding your travel CRM directly — no inbox copy-paste.

By the Tripdocks team · Last updated

Any WordPress form that can send a webhook can feed Tripdocks. Create a webhook in Tripdocks, map your form's fields once, and paste the webhook URL into your form's webhook setting. Each enquiry then lands in your lead queue with the trip details your form collects.

How it works

  1. In Tripdocks, add a webhook under Settings → Integrations → Webhooks and name it after the form.
  2. Map the form's fields: name, email, phone, travel dates, nights, and number of adults and children. Store anything else, like destination or budget, as form data.
  3. Copy the webhook URL into your form plugin's webhook action. Elementor Pro forms include a Webhook action; WPForms and Gravity Forms offer webhook add-ons.
  4. Submit a test enquiry and check your lead queue.

What you need

  • A WordPress form that can send a webhook (built in, or through an add-on).
  • Dates sent as yyyy-MM-dd, or the format noted in the mapping so it parses correctly.

What your team gets

  • Enquiries in your lead queue within seconds of submission.
  • Nested form data supported through dot notation (for example user.contact.email).
  • Duplicate submissions within 5 minutes filtered out, while the visitor still sees a success message.
  • Rate limits of 30 leads a minute and 500 an hour per webhook, which protects you from spam bursts.

Step-by-step instructions are in the Webhooks guide. Leads from every connected channel land in the same queue — see lead management.

Related integrations

Frequently asked questions

Which WordPress form plugins work with Tripdocks?
Any plugin that can send an HTTP POST to a URL. Elementor Pro forms have a built-in Webhook action, and WPForms and Gravity Forms offer webhook add-ons. Tripdocks accepts JSON, form-encoded, and multipart data.
What if my form uses dd/MM/yyyy dates?
Set that format in the field mapping and Tripdocks parses it correctly. ISO 8601 (yyyy-MM-dd) is recommended.