zaus

Oh wait, I think I just figured out the problem — you’ve left the default “wrapper” alone (value = post), meaning it’s wrapping your request under the “post” key:

[body] => {"post":{"FIRST_NAME":"my name","LAST_NAME":"my name"}}

Try emptying out that field.

Sorry, you can’t use the Dynamic Fields macros in the URL (that would be a useful feature; please submit an issue). Also, the macros like ##GET:{CampaignID}## just result in the value, not including the arg name, so you would have needed to use &CampaignID=##GET:{CampaignID}## anyway.

Does it have to be part of the URL? I’m pretty sure Velocify can grab it from posted parameters, so you can put it in the mapping “as usual”.

Incidentally, you don’t need the Dynamic Text Extension plugin if you’re using my Dynamic Fields addon, or vice versa — I assume you have both just to troubleshoot?

Good question. After reading their changelog, I don’t have any reason to think my plugin wouldn’t continue to work with GF v2. Most of the functionality in my plugin involves hooking to the contact form’s “before_send” filter/action, and I didn’t see any changes mentioning gform_pre_submission_filter or specifically how it makes the submission data available, so we should be fine.

I would ask that you try installing the beta plugin and let me know if there are any problems; I would myself but ironically I don’t have a GF license.

Yeah that weird bug had been around forever, sorry. I can’t remember if you can save and refresh the page or you need to delete/add another service is the workaround.

Glad I could help!

I think you’re on the right track. All of the other form plugins (CF7, GF, Ninja) follow a loose ‘plugin’ architecture — https://github.com/zaus/forms-3rdparty-integration/tree/master/plugins
which are “registered” here https://github.com/zaus/forms-3rdparty-integration/blob/master/includes.php

Since CFDB basically intercepts the $_POST array, I think adapting the GF plugin would be the right place to start: https://github.com/zaus/forms-3rdparty-integration/blob/master/plugins/gravityforms.php
“Just” fill in the appropriate functions/properties, eg)

• BEFORE_SEND_FILTER — give the cfdb_submit hook name
• GET_PLUGIN_FORMS — might be weird, basically need to give a list containing a static placeholder that GET_FORM_ID will also return, since you don’t know what to target
• IS_PLUGIN_FORM — also weird, probably need to confirm the structure of $form matches whatever came in to the cfdb_submit hook

If you figure something out, publish it as a plugin and I’d be happy to link to it.

Since it’s a “simple mapping issue”, assuming resolved.

*sigh* It’s because you’re not mapping correctly. I swear I stickied this before…I’ll remake the summary.

https://wordpress.org/support/topic/its-not-sending-data-help-read-this-first

Specifically, Ninja forms doesn’t provide a ‘machine name’ for the field (the “ninja_forms_field_17” you were expecting) but rather just the ID, as you can see in the “*** Post (Form) ***” section of the debug email. My plugin also includes/can use the field label to make reusing services easier across forms. Just pick the appropriate keys from the “*** Post (Form) ***” section to use as your ‘Source’ fields.

My plugin uses wp_remote_post, so you’d need to hook to ...service_filter_args to add additional details like cookies. Or you could use my Dynamic Fields addon to include specific session/cookie data within the integration post.