Kainoto Webhook for Contact Form 7
Kainoto Webhook for Contact Form 7 is a lightweight WordPress plugin that extends Contact Form 7 functionality by sending form submission data to specified webhook URLs. The plugin operates asynchronously, ensuring your website’s performance isn’t affected by external API response times. Key Features Asynchronous Processing: Sends webhook data without waiting for response, maintaining optimal site performance Easy Configuration: Simple webhook URL setup directly in Contact Form 7 admin panel JSON Format: Sends form data in clean JSON format for easy processing URL Validation: Built-in validation ensures only proper URLs are accepted No Response Dependency: Fire-and-forget approach prevents external service issues from affecting your forms Lightweight: Minimal code footprint with no unnecessary bloat Perfect For CRM integrations Email marketing services Custom analytics tracking Third-party notification systems API-based workflow automation Real-time data synchronization How It Works Install and activate the plugin Edit any Contact Form 7 form Navigate to the new “Webhook” tab Enter your webhook URL Save the form That’s it! Now every form submission will automatically send the data to your specified webhook URL in JSON format. Technical Details Hooks into Contact Form 7’s submission process after validation but before email sending Sends POST requests with JSON payload containing all form field data Uses WordPress HTTP API for reliable delivery 15-second timeout with non-blocking execution Sanitizes and validates all webhook URLs Developer Information Hooks and Filters The plugin provides several hooks for developers: wpcf7_editor_panels – Adds the webhook panel to CF7 admin wpcf7_save_contact_form – Saves webhook settings wpcf7_submit – Sends webhook data after form submission Code Example `php // Example webhook endpoint (PHP) $json = file_get_contents(‘php://input’); $data = json_decode($json, true); // Process form data foreach($data as $field => $value) { // Handle each form field error_log(“Field: $field, Value: $value”); } ` Support For technical support, feature requests, or bug reports, please visit: https://kainoto.com Privacy Policy This plugin does not collect, store, or transmit any personal data beyond what is explicitly submitted through Contact Form 7. All data handling is controlled by your webhook endpoint configuration.
REST API Enabler
Like this plugin? Please consider leaving a 5-star review. By default, custom post types and custom fields are not accessible via the WordPress REST API. REST API Enabler allows you to: Enable the WP REST API for custom post types and specify WP REST API custom endpoints. Choose which custom fields to include in WP REST API responses for posts, pages, and custom post types. All enabled custom field data is included in the REST API response, nested under the rest_api_enabler key, like so: [ { "id": 179, "date": "2016-07-03T18:06:50", "title": { "rendered": "Test Job" }, . . . "rest_api_enabler": { "custom_meta_1": "Value 1", "custom_meta_2": "Value 2", "custom_meta_3": [ "Array value 1", "Array value 2" ] } } ] Note: prior to verion 1.1.0, all meta keys were included as top-level keys in the API response. Additionally, all values were returned as arrays, regardless of whether the original value was actually an array. This functionality is now deprecated as it risks key-name collisions. Please reference the rest_api_enabler top-level key instead. Usage Activate the plugin, then go to Settings → REST API Enabler in the admin. Click the Post Types tab to enable/disable post types and customize their endpoints. Click the Post Meta tab to enable/disable post meta (custom fields). NOTE: by default, the plugin does not display settings for protected post meta (post meta that begins with an underscore and is intended for internal use only). If you wish to include protected post meta in the plugin settings, you can use the rae_include_protected_meta filter to do so. The following code can be placed in your theme’s functions.php file, or in a custom plugin (on init priority 10 or earlier): add_filter( 'rae_include_protected_meta', '__return_true' );
