zaus

Any luck?

Glad I could help! Don’t forget to give the plugin a good rating too!

You’ll need to attach the entire debug email, not just the ‘post to service’ section; otherwise I have no idea what’s going on.

To upgrade deprecated WordPress Plugin [CF7-3rdparty Integration](http://wordpress.org/plugins/contact-form-7-3rd-party-integration/) to the new version [Forms 3rdparty Integration](http://wordpress.org/plugins/forms-3rdparty-integration/).

From discussion at http://wordpress.org/support/topic/how-to-upgrade-from-old-version-to-this-one?replies=1

Your mileage may vary…

0. You should have both plugins enabled with at least one service configured and saved. This is so you have both complete sets of options available for comparison, because you may have to add some extra properties beyond just copy/paste.
0. Make sure to change the ‘secret expected key’ value
1. Upload this to your plugins folder, or
2. Upload somewhere, then include in functions.php with include('path/to/Forms-3rdparty-Migrate-Hack.php') — or just paste it directly into functions.php in the WP editor
3. Go to your site, but add ?forms-3rdparty-migrate=your-temporary-secret-plz-change-this to view the ‘editor’
* add &raw=true will print the whole array(s) out for extra debugging
4. Scroll to the bottom of the page
5. Copy the ‘old’ textarea into the ‘new’ textarea **if you haven’t configured** Forms-3rdparty yet (this will overwrite everything) If you have already configured some services, you’ll need to copy those parts and insert them into the old value.
* You don’t need to change the old keys (cf7) to the new (src) — this will do it automatically
6. Make sure to add any additional properties present in the ‘new’ field are added, otherwise you might get some PHP warnings when you go back to the Forms-3rdparty admin page. This part might not be necessary if you don’t have PHP warnings turned on.
7. Test it first with the “Test” button — see what the serialized values look like.
8. When you’re happy things look about right, use the “Update” button.
9. Check the admin page to make sure your settings are all there.
10. Try the form.

Yeah that seems pretty straightforward.

1. use https://bpi.briteverify.com/emails.json as the service url
2. map the CF7 email field (something like the default your-email) to the 3rdparty address field
3. add another map with ‘Is Value’ checked, put your api key in the ‘Forms’ column, and apikey in the ‘3rdparty’ column
4. In the ‘success condition’ textbox add "status":"valid", which should only show up in the response if your submission worked.

Sorry for the delay — yes you can use this plugin to post to an API, and you can specify any url as the endpoint (including posting to an xml extension).

You’ll also need the 3rdparty Xml Post plugin to wrap the response in the hl7message / data xml tags.

You might need to write a hook for either Forms3rdPartyIntegration_service_filter_post or Forms3rdPartyIntegration_service_filter_args to wrap the args individually rather than using the posted tags.

Make sure to turn on ‘debug mode’ to investigate the posted result and response.

Well. Unfortunately that response doesn’t really tell us anything. You might need to take it up with Salesforce to figure out the problem. Are you sure you’re submitting all of the fields originally found on the Salesforce form? I think I’ve seen some CRMs reject leads if they don’t contain at least a minimal set of ‘required’ fields, whatever those may be.