by danielboven 1 (0 reviews)

Webhook Signature add-on for Gravity Forms

Name: Webhook Signature add-on for Gravity Forms
Author: danielboven

Add a signature HTTP header to webhook requests to prevent man-in-the-middle and replay attacks.

Webhook Signature add-on for Gravity Forms ranks #63,798 among WordPress.org plugins with 1+ active installations, is #1,653 of 2,599 in the Contact Forms category, a 1/5 rating from 0 reviews, and was last updated Feb 17, 2021. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 5.6 (Current: 7.1.2)

vtrunk Current Version vtrunk

Updated 5 years ago Last Update on 17 Feb, 2021

Refreshed 8 hours ago Last Refreshed on

#1,653 of 2,599 in Contact Forms No update in over a year

View on WordPress.org

Rank

#63,798

-27902 this week

Active Installs

-66.7%

KW Avg Position

N/A

— No change

Downloads

+2 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

63,098

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

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #63,798

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: trunk
Last Updated: Feb 17, 2021
Requires WP: 4.0+
Tested Up To: 5.6
PHP Version: 7.0 or higher
Author: danielboven

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

forms gravity request verify webhook

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,758

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

WPForms - AI Form Builder for WordPress - Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Jetpack - WP Security, Backup, Speed, & Growth

3M+ installs

#18

MC4WP: Mailchimp for WordPress

1M+ installs

#34

Hostinger Reach - AI-Powered Email Marketing for WordPress

Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

700K+ installs

#83

Joinchat - Enhanced "click to chat"

700K+ installs

#88

View all Contact-forms plugins

Frequently Asked Questions

Common questions about Webhook Signature add-on for Gravity Forms

Navigate to the plugin settings. Copy the key in the Public Key field to your own application (receiver). Use it to verify the signature.

Keys that are generated by the plugin have the following format: - Digest algorithm: SHA256 - Private key type: RSA (OPENSSL_KEYTYPE_RSA) - Private key bits: 1024 It is therefore advised that in case you use custom keys, you use a similar format, since no other format than the one above has been tested. You also have to include the BEGIN and END lines, for example: Public Key: -----BEGIN PUBLIC KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXX -----END PUBLIC KEY-----

I'd love to hear your bug reports, feature suggestions and any other feedback! Please head over to the GitHub issues page to search for existing issues or open a new one. While I'll try to triage issues reported here on the plugin forum, you'll get a faster response (and reduce duplication of effort) by keeping everything centralized in the GitHub repository.