Search Over 30,000 FREE Plugins from the Official WordPress Plugin Directory Repository

Forms: 3rd-Party Xml Post

Converts submission from Forms 3rdparty Integration to xml/json, add headers, or nest fields.

Converts external submission from Forms: 3rdparty Integration plugin to an XML or JSON post; optionally can add custom headers (to allow SOAP submissions) or transform/combine separate fields into nested values.

This plugin can turn the 3rdparty mappings into XML elements, so that each form post will be the value (or attribute) of an XML element.

Author zaus, leadlogic
Contributors zaus, leadlogic
Tags 3rd-party service, cf7, contact form, contact form 7, CRM, form, GF, gravity forms, json, json webservice, mapping, nested fields, remote request, services, soap, soap webservice, xml, xml webservice, xpost

None available.

  1. Unzip, upload plugin folder to your plugins directory (/wp-content/plugins/)
  2. Make sure Contact Form 7 or Gravity Forms is installed
  3. Make sure Forms: 3rdparty Integration is installed
  4. Activate plugin
  5. Go to new admin subpage "3rdparty Services" under the CF7 "Contact" menu or Gravity Forms "Forms" menu and configure services + field mapping.
  6. Configure the new "Xml Post" section to choose which services send as xml and/or determine special headers (given as a url querystring).
  7. Nest fields by separating nodes with /, and indicate attributes with @. Numeric indexes by themselves will result in repetition of the parent element (ex. item/%i/sub could make <item><sub /></item><item><sub /></item>).


  • new string replacement format using mustache-style token placeholders {{3rdparty}}


  • actually fix #24 parsing xml in root


  • fix: bug parsing existing xml root
  • allow shortcodes in root


  • removed somewhat useless numerical index prefixing (n0, n1, nEtc)
  • replaced with element repetition instead


  • ignores xml root when considering escaped backslashes (compatibility break -- please update your setting accordingly)
  • 'mask' format -- greater flexibility and control over field/wrapper
  • shortcodes in header; base64 shortcode


  • autoclose option
  • decided it was good enough to be v1



Can post body as json instead


Fixed GitHub issue #3

  • each plugin setting is only applied to that specific service if it has a value
  • removed default post wrapper unless sending as xml (and if you send XML you should specify a wrapper)


Can nest regular post fields even when not submitting XML.


  • Element nesting, attributes
  • reworked "xmlify" using recursive SimpleXMLElement


Base version - xml and header transformation

I need help

Submit an issue to the GitHub issue tracker in addition to / instead of the WP Support Forums.

How do I add / configure a service?

See "base plugin" Forms: 3rdparty Integration.

How do I set headers

Provide the list of headers as though they were a URL querystring, so that

Content-Type: something X-Special-Header: something-else

would be given as


You may also use shortcodes such as base64 in the header.

How do I nest elements?

Separate element names within the same 3rdparty field mapping using /, so that in order to make:

<credentials type="123">

you would use credentials/@type, credentials/user and credentials/pass, respectively.

Note: You may nest and wrap elements even if not transforming into XML; they will be submitted as multi-dimensional arrays like:


How do I repeat elements?

As of v1.3, if there is a standalone numerical index it will cause repetition of the "parent" element.

ex) If the post is:

item => array (
        0 => value1,
        1 => value2,
        2 => value3

it will result in


You can accomplish this with the Forms-3rdparty separator [%] to place your index appropriately.

How do I set xml prolog attributes?

Just enter the entire root xml in the field, a la

How do I autoclose/not autoclose empty values?

To produce <SomeTag />, make sure the "Autoclose" option is enabled. To produce <SomeTag></SomeTag>, make sure the "Autoclose" option is unchecked.

How do I completely customize the xml/wrappers/transform?

Use the 'Mask' format, which allows you to specify the result exactly as you want via string replacement (sprintf), or the 'Replace' format which will replace string tokens ({{3rdparty}}). Useful for complex XML.

The 'Root Element' field will now be treated as a string-replacement mask (a la sprintf for "Mask" or str_replace for "Replace"), so make sure to include the post body with the appropriate placeholder(s) (%s for "Mask", {{3rdparty_Fields}} for "Replace"). For 'Mask' format, each '3rd-Party Field' will also be treated the same, using %s to indicate where the submission value should go. For 'Replace' format, repeating fields are not handled -- it essentially looks for instances of each "3rd-Party Field" column and replaces it with the corresponding input value.

Version 1.4

Requires WordPress version: 3.0 or higher

Compatible up to: 4.6.3

Last Updated 03 Oct 2016

Date Added: 23 Feb 2014

Plugin Homepage


5 stars
2 ratings


Not Enough Data

Works: 0
Broken: 0