raintech357

RT Webhook for Gravity Forms allows you to send form submission data to any external URL or service (like Zapier, Make.com, or your own custom API) with granular control.
<h3>Advanced Features:</h3>
<ul>
<li>Multiple Webhooks: Assign multiple webhooks to a single form.</li>
<li>Dynamic Field Mapping: Select Gravity Forms fields from a dropdown and map them to custom JSON keys.</li>
<li>Conditional Logic: Trigger webhooks only when specific field values match your criteria.</li>
<li>Custom HTTP Headers: Add authorization tokens or other custom headers (e.g., Bearer tokens).</li>
<li>Logging System: Keep track of the last 10 webhook requests with full URLs, headers, payloads, and server responses.</li>
<li>Support for Multiple Methods: Use POST, GET, or PUT requests.</li>
</ul>

RT Webhook for Gravity Forms

An advanced webhook integration for Gravity Forms with field mapping, conditional logic, and custom headers.

Jason Coleman

Paid Memberships Pro

Integrate activity on your membership site with thousands of other apps via Zapier (requires Paid Memberships Pro). <a href="https://www.paidmembershipspro.com/add-ons/pmpro-zapier/" rel="nofollow ugc">Extended documentation can be found at PaidMembershipsPro.com</a>.
Our Zapier integration includes the following triggers and actions to send information to Zapier and connect with third-party apps. A “Trigger” will send data to Zapier when changes are made on your Membership site. An “Action” will process incoming data when a change is sent to your Membership site via Zapier and a connected third-party app.
<h4>Triggers</h4>
New Order
Updated Order
Changed Membership Level
After Checkout
<h4>Actions</h4>
When creating the Action component of a Zap, use the webhook URL provided on the Actions tab of the PMPro Zapier settings and pass in parameters matching those given below.
add_member
The following parameters can be passed into the add_member Action:
<ul>
<li>user_email (required)</li>
<li>level_id (required)</li>
<li>user_login</li>
<li>full_name</li>
<li>first_name</li>
<li>last_name</li>
</ul>
Note that user_email and level_id are required parameters; you must also pass in at least one of user_login, full_name, first_name, or last_name.
change_membership_level
The following parameters can be passed into the change_membership_level Action:
<ul>
<li>user_id</li>
<li>user_email</li>
<li>user_login</li>
<li>level_id (required)</li>
</ul>
Note that level_id is a required parameter; you must also pass in at least one of the following user identifiers is also required: user_id, user_email, or user_login.
add_order
The following parameters can be passed into the add_order Action:
<ul>
<li>user_id</li>
<li>user_email</li>
<li>user_login</li>
<li>level_id</li>
<li>subtotal</li>
<li>tax</li>
<li>couponamount</li>
<li>total</li>
<li>payment_type</li>
<li>cardtype</li>
<li>accountnumber</li>
<li>expirationmonth</li>
<li>expirationyear</li>
<li>status</li>
<li>gateway</li>
<li>gateway_environment</li>
<li>payment_transaction_id</li>
<li>subscription_transaction_id</li>
<li>affiliate_id</li>
<li>affiliate_subid</li>
<li>notes</li>
<li>checkout_id</li>
<li>billing_name</li>
<li>billing_street</li>
<li>billing_city</li>
<li>billing_state</li>
<li>billing_zip</li>
<li>billing_country</li>
<li>billing_phone</li>
</ul>
update_order
The following parameters can be passed into the update_order Action:
<ul>
<li>order, order_id, code, or id (required)</li>
<li>user_id</li>
<li>user_email</li>
<li>user_login</li>
<li>level_id</li>
<li>subtotal</li>
<li>tax</li>
<li>couponamount</li>
<li>total</li>
<li>payment_type</li>
<li>cardtype</li>
<li>accountnumber</li>
<li>expirationmonth</li>
<li>expirationyear</li>
<li>status</li>
<li>gateway</li>
<li>gateway_environment</li>
<li>payment_transaction_id</li>
<li>subscription_transaction_id</li>
<li>affiliate_id</li>
<li>affiliate_subid</li>
<li>notes</li>
<li>checkout_id</li>
<li>billing_name</li>
<li>billing_street</li>
<li>billing_city</li>
<li>billing_state</li>
<li>billing_zip</li>
<li>billing_country</li>
<li>billing_phone</li>
</ul>
has_membership_level
The following parameters can be passed into the has_membership_level Action:
<ul>
<li>user_id</li>
<li>user_email</li>
<li>user_login</li>
<li>level_id (required)</li>
</ul>
Note that level_id is a required parameter; you must also pass in at least one of the following user identifiers is also required: user_id, user_email, or user_login.

Paid Memberships Pro – Zapier Add On

Integrate activity on your membership site with thousands of other apps via Zapier.

RT Webhook for Gravity Forms vs Paid Memberships Pro – Zapier Add On