Delimiter format handling has changed. May be a breaking change if you were using it "wrong" (according to how it was previously described).<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":[],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[125390,358,1150,361,4605],"plugin_category":[42,49],"plugin_contributors":[80258],"plugin_business_model":[],"class_list":["post-68671","plugin","type-plugin","status-publish","hentry","plugin_tags-3rd-party-service","plugin_tags-contact-form","plugin_tags-crm","plugin_tags-form","plugin_tags-mapping","plugin_category-contact-forms","plugin_category-maps-and-location","plugin_contributors-zaus","plugin_committers-zaus"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/forms-3rd-party-inject-results.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Allows you to include results from a Forms 3rdparty Integration<\/a> submission by flattening the response and inserting it within the original contact form submission.<\/p>\n\n\n\n
\/wp-content\/plugins\/<\/code>)<\/li>\nResponse\/Body\/SomeKey<\/code>, one per line.\na. If the response is JSON or XML it will scan the elements\/keys according to the segments you've entered; in the above example it will look for { Response: { Body: { SomeKey: \"foobar\" } } }<\/code> and include \"foobar\" with the submission.<\/li>\nResponse\/Body\/SomeKey=the_alias<\/code>, where the_alias<\/em> is the contact form field to override.\na. With Gravity Forms, fields should be overwritten using aliases like input_X<\/code> where 'X' is the field's id.<\/li>\n<\/ol>\n\n\n