Back to Integrations Guides

This guide applies to:

  • Basic Edition
  • Plus Edition
  • Pro Edition
  • Business Edition


In this guide, we want to review some popular Gravity Wiz Perks that work nicely with the Simply Schedule Appointments and Gravity Forms integration.

We’re going to cover the following Perks:

  • Populate Anything
  • Limit Submissions
  • Preview Submission

Visit our Demo Booking Form, where we showcase the Populate Anything and Preview Submissions perks.

Populate Anything Perk

The fabulous Populate Anything Perk makes it easy to display live Appointment information from your form or the SSA databases using the Dynamic Database Objects and Live Merge Tag features.

Dynamic Database Objects – Populate Choices and Values

Any field that supports the dynamic population feature, such as radio buttons, checkboxes, dropdowns, and text-based fields, can now be automatically filled in with information directly from the Simply Schedule Appointment databases.

This is available for both populating choices and populating values dynamically.

Simply select the Database option in the dynamic population Type dropdown. Select any of the SSA database tables from the Table dropdown. The tables are prefixed with wp_ssa_.

Here are some SSA database tables you can use:

  • wp_ssa_appointments: Stores all of the bookings. As soon as a user selects a time slot in the Appointment field in your Gravity Form, it’s stored here.
  • wp_ssa_appointment_types: Stores the appointment type information, such as the title and settings.
  • wp_ssa_staff: Stores team member information such as their name and email.
  • wp_ssa_staff_appointments: Table that stores the relationship between the appointments table and the staff table.

You can also use the Appointment field from your Gravity Form to Filter the results. Each Appointment field returns the Appointment ID; in the database tables, it’s just id.

Next, you’ll need to select the Value (and the Label if you’re populating choices) that you’d like to use to populate the field. It will show you the number of results found so you can double-check to ensure you’re retrieving the results you expect.

And lastly, you can optionally choose to Order the results you grab from the SSA database tables by a specific property.

Live Merge Tags, Galore!

To enter a Live Merge tag, simply prefix the SSA merge tag with the @ symbol.

We have a guide listing all available SSA Gravity Form merge tags.

For example, to enter the Appointment Type Title into a Field Label, use this merge tag:

Displaying the Live Merge Tags for the Simply Schedule Appointments field in the Gravity Form editor.

(Optional) Fallback Modifier

The Live Merge Tags feature also includes a Fallback modifier; this allows you to display custom text before the Live Merge Tag is populated.

The Fallback Modifier is only compatible with the plain SSA merge tag; this doesn’t work alongside the SSA modifiers.

@{FIELD_NAME:FIELD_ID:fallback[Please fill in the form]}

Limit Submissions Perk

Simply Schedule Appointments doesn’t have any built-in functionality to limit bookings or submissions. If you need to prevent users from over-booking in your schedules, we offer two workarounds:

  • Use the Limit Submissions Perk, duh! The only drawback is that this perk can’t limit the literal availability in booking calendars (ex., Only one submission per IP, no limit on the SSA calendar availability options.)
  • Use our mini-plugin to Limit Bookings. The limitation with this option is that this only works for logged-in users and needs a bit of custom coding to meet your limitation needs. (ex. Only one booking per calendar month in SSA.) This works with SSA as a standalone booking form.

1. Create a Limit Feed for Your Form

After Installing the Limit Submission Perk on your site, you should have a new Limit Submission Feed tab in your Form Settings. Start by clicking on Add New.

Now, you can edit the General Settings and Rules for your Limit Submissions Feed.

The Limit Submissions Feed editor, includes the feed name, submission limit, time period, limit message, and rules.

2. Setting up the Limit Submissions Feed

We’ll list a quick overview of all the settings; for a more in-depth explanation of the General Settings and Rules, visit the Gravity Wiz documentation.

Fill in the fields accordingly:

  • Limit Feed Name: Name your feed something to help you remember its purpose. Since you can have multiple Limit feeds, keeping the Names organized is best.
  • Submission Limit: The max number of entries that can be submitted if all of the rules are met during the Time Period you set.
  • Time Period:
    • Forever
    • Time Period ex. Three days.
    • Calendar Period ex. Per month or week.
    • Form Schedule configured in the Form Settings > Restrictions, the period where the Gravity Form is active.
  • Limit Message: Share some context with the user if they meet the Limit Submission threshold.
  • Rules: Specify when the Limit Feed kicks in. You can limit by:
    • The user’s IP address
    • WordPress user IDs
    • URL on which the form was submitted
    • WordPress roles, ex. Subscribers, Editors.
    • Field Values

Check out their awesome documentation for this perk. It’ll give you more information on how to test with the Limit Submissions shortcode and how to set up Limit Reached Notifications.

Some Additional Notable Perks

Preview Submissions Perk

We love the Preview Submissions perk because it allows users to quickly review their form entry before submission. And if they spot that they need to make a change, like finding a different appointment time, they can quickly go back and update the fields before submission.

The Preview Submissions Perk in action, it displays all of the previously entered information in the form before submission.

Still stuck?

File a support ticket with our five-star support team to get more help.

File a ticket

  • Please provide any information that will be helpful in helping you get your issue fixed. What have you tried already? What results did you expect? What did you get instead?
  • This field is for validation purposes and should be left unchanged.

Related Guides