New entry detection

Gravity Forms records every field a visitor fills in on a WordPress form, from contact details to open text answers, as soon as the form is submitted. A Beam agent watches the form for a new entry and reads the fields the account owner has marked as relevant, rather than a person checking the WordPress dashboard for new submissions. Where the entry matches an approved rule, such as a request for a callback or a support topic, the agent opens the corresponding record in a connected tool and notifies the right channel. Entries that mix multiple requests, or include a field the agent cannot map to an existing rule, get left for a person to read directly.

Conditional field logic

A Gravity Forms form can show or hide fields based on earlier answers, so two visitors filling out the same form may end up submitting different sets of fields depending on their choices. A Beam agent reads the entry as it was actually submitted, field by field, rather than assuming every entry follows the same shape. This lets the agent apply the right rule for that specific path, such as routing a refund request differently from a general question, without a person first checking which version of the form the visitor saw. Entries where the field combination does not match any approved rule are passed to a person to interpret.

Multi-form account coverage

A WordPress site can run several Gravity Forms at once, covering contact requests, event signups, and support tickets from the same install. A Beam agent watches the specific forms an account owner has connected, rather than every form on the site, and applies a separate rule set to each one so a contact form entry is not handled the same way as a signup. Where account permissions allow it, the agent notifies a different channel or record depending on which form produced the entry. Forms that have not been explicitly connected are left alone, and any entry the agent cannot classify against a known rule goes to a person.