by
Aurovrata Venet
4.8 (48 reviews)
Post My CF7 Form
This plugin enables the mapping of your CF7 forms to custom posts, including featured images, files, meta-fields and taxonomies
Post My CF7 Form ranks #4,721 among WordPress.org plugins with 2,000+ active installations, a 4.8/5 rating from 48 reviews, and was last updated Aug 1, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1.1)
v7.1.0
Current Version v7.1.0
Updated 1 month ago
Last Update on 01 Aug, 2026
Refreshed 12 hours ago
Last Refreshed on
Top 10% by installs
Downloads -7.8% this week
Rank
#4,721
+3 this week
Active Installs
2K+
-30.5%
KW Avg Position
21.8
—
No change
Downloads
95.1K
+23 today
Support Resolved
0%
—
No change
Rating
96%
Review 4.8 out of 5
4.8
(48 reviews)
Next Milestone 3K
2K+
3K+
533
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 133 more installs to reach 3K+
Rank Changes
Current
#4,721
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.8
48 reviews
Overall
96%
5
45
(94%)
4
0
(0%)
3
2
(4%)
2
0
(0%)
1
1
(2%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
0
Resolved
1
Unresolved
0%
Resolution Rate
Security History
Source: WPVulnerability1 known vulnerability on record · 1 in the last 24 months · checked 1 month ago
-
Post My CF7 Form [post-my-contact-form-7] < 7.0.0
CVE-2026-59534 · Fixed in v7.0.0
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 7.1.0
- Last Updated
- Aug 01, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Aurovrata Venet
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.8
- Reviews
- 48
- Support Threads
- 1
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners and developers using Contact Form 7 who need submitted form data saved as structured content. It solves the problem of CF7 not natively supporting mapping form fields to posts, meta fields, taxonomies, and featured images for management in the dashboard.
- Maps form fields to posts
- Featured image/file attachment mapping
- Unlimited meta-field mapping
- Taxonomy mapping with auto-population
- Form keys for portability
- Multiple draft submissions management
- Custom filters per form field
- Compatible with Smart Grid-Layout Designs
Frequently Asked Questions
Common questions about Post My CF7 Form
Place the following in your functions.php file, add_filter('cf7_2_post_form_append_output', 'redirect_on_submit', 10, 3); function redirect_on_submit($script, $attr, $nonce){ //$attr cf7 shortcode attributes to check if this is the correct form. $url = site_url('/submitted'); //page slug to redirect to. $url = add_query_arg( array('cf72post' => $nonce,), $url); $url = esc_url($url); $script .= '<script>'.PHP_EOL; $script .= 'document.addEventListener( "wpcf7mailsent", function( event ) {'.PHP_EOL; $script .= ' var save = document.getElementsByClassName("cf7_2_post_draft");'.PHP_EOL; $script .= ' if(save.length == 0 || "false" === save[0].value){'.PHP_EOL; $script .= ' location = "'.$url.'";'.PHP_EOL; $script .= ' }'.PHP_EOL; $script .= '}, false );'.PHP_EOL; $script .= '</script>'.PHP_EOL; return $script; }
Now the submitted form is saved to a post and its ID is stored in a transient field by the plugin. You can access this transient field with the following code in your page template, if(isset($_GET['cf72post'])){ $post_id = get_transient($_GET['cf72post']); echo 'form submission saved to post:'.$post_id; } If you wish to redirect to the newly saved post (assuming it is published, see FAQ #16), if(isset($_GET['cf72post'])){ $post_id = get_transient($_GET['cf72post']); //get the link to the new post, $url = get_permalink($post_id); if ( wp_redirect( $url, 200 ) ) { exit; } echo 'unable to redirect, maybe the post wasn't published'; }
In the Contact Form 7 table list you will notice a new column has been added which allows you to create a new custom post mapping. This will take you to a new screen where you will see your existing fields listed in select dropdowns. Map your form fields to either a default field (eg title, content, excerpt, or author), or create a custom (meta) field, or even create a new taxonomy for your post. Once you have mapped your form you can toggle its status from on to off. In the off position, the plugin will no longer capture form submissions and save them to the mapped post.
You can simply modify the mapping at any given time, however if a mapping has been live and saving submissions to your post, then it is not recommended to make changes. Unless you have a fair understanding of WordPress posts and meta-fields structures and how these are saved in the database, I highly recommend that you delete any existing posts that may have been saved from form submissions that used the previous mappings. Failing to do this without a proper understanding of the changes you are making to an existing mapping with previously saved post submissions could lead to difficult errors to debug and fix once you start creating post submissions that have a different mapping. Consider yourself warned!
Simply toggle the status to off.
You create a new taxonomy and map your field to it. Note however that only select/checkbox/radio type of fields can be mapped to taxonomies. Once mapped and published you will see your taxonomy appear in your custom post menu. You can add terms to your taxonomy and these will be made pre-filled into your mapped field. Users can select a term and when the form is submitted, the post will be created with those terms assigned to it. (see screenshot 9 for more details.)
You need to use a special filter for this, 'cf7_2_post_filter_taxonomy_registration-{$taxonomy_slug}', see the Filter & Actions section for more details.
You may have noticed that in addition to mapping a post field or taxonomy to one of your form fields, you can also use a filter to hook your own custom values. In the case of taxonomies, you can actually map a form submission to a specific set of terms depending on the submission of other fields.
This is a little more complex. You will need to create an input field in your form in which users can submit a new term. You will then need to hook the action cf7_2_post_form_mapped_to_{$post_type} which is fired right at the end of the saving process. The hook parses the newly created $post_ID as well as the submitted $cf7_form_data form data array. You can then check if your user has submitted a new value and include it in taxonomy and assign the new term to the post.
There are are 2 filters provided to achieve this. In both cases, these filters are fired if the form is mapped to a post type only. The default behaviour is for the plugin to seek any draft saved form values for teh current user. A form is saved (draft) if the save button tag is used which allows a user to save a partially filled form and to submit it at a later stage. If a draft form is found for the current user, then the first filter will not be fired, the cf7_2_post_filter_cf7_field_value is fired for each field, and a helper code is available in the mapping edit admin page (see the Screenshot #8), filter #7. cf7_2_post_form_values is fired at the end of values pre-fill process, and allows all the values to be filtered, including those that may have been loaded if the current user as a draft form saved. add_filter('cf7_2_post_form_values', 'simple_cf7_form_values' ,10,4); function simple_cf7_form_values($field_values, $cf7_id, $post_type, $ck7_key){ if( 'my-form'!=$ck7_key ) return $field_values; //check this is the correct form. $field_values['your-name'] = 'prefilled name'; return $field_values; } If you have a WordPress page template that contains a CF7 form and want to change the field values from one page request to another, this can be done using the cf7_2_post_form_values filter (see Filter & Actions for more details). You will need to create an anonymous function on this filter and pass the CF7 id form your shortcode which you can automatically scan for form your page content. In the example below I assume that the page contains the default 'Contact Me' CF7 form which I want to pre-fill if a user is logged in, $content = get_the_content(); //let's find our shortcode preg_match_all( '/' . get_shortcode_regex() . '/s', $content, $matches ); $args = array(); if( isset( $matches[2] ) ){ foreach( (array) $matches[2] as $key => $shortcode ){ if( 'contact-form-7' === $shortcode ) $args[] = shortcode_parse_atts( $matches[3][$key] ); } } //here I am assuming there is a single form on the page, if you have multiple, you will need to loop though each one if(!empty($args) && isset($args[0]['id'])){ $short_id = $args[0]['id']; $values = array(); if(is_user_logged_in()){ $user = wp_get_current_user(); $values['your-name']= $user->display_name; $values['your-email'] = $user->user_email; if(!empty($subject)){ $term = get_term_by('id', $subject, 'project-type'); $values['your-message'] = 'Dear Hexagon,'.PHP_EOL.'I request you to create a new '.rtrim($term->name,'s') ; } //now lets filter the values add_filter('cf7_2_post_form_values', function($field_values, $cf7_id) use ($short_id, $values){ if($short_id == $cf7_id ){ return $values; } }, 10,2); } }
