Title: Broadcaster Auto Responder for Gravity Forms Author: fullworks Published: May 29, 2026 Last modified: May 29, 2026 --- Search plugins ![](https://ps.w.org/broadcaster-auto-responder-for-gravity-forms/assets/banner- 772x250.png?rev=3554230) ![](https://ps.w.org/broadcaster-auto-responder-for-gravity-forms/assets/icon-256x256. png?rev=3554230) # Broadcaster Auto Responder for Gravity Forms By [fullworks](https://profiles.wordpress.org/fullworks/) [Download](https://downloads.wordpress.org/plugin/broadcaster-auto-responder-for-gravity-forms.1.1.5.zip) * [Details](https://test.wordpress.org/plugins/broadcaster-auto-responder-for-gravity-forms/#description) * [Reviews](https://test.wordpress.org/plugins/broadcaster-auto-responder-for-gravity-forms/#reviews) * [Installation](https://test.wordpress.org/plugins/broadcaster-auto-responder-for-gravity-forms/#installation) * [Development](https://test.wordpress.org/plugins/broadcaster-auto-responder-for-gravity-forms/#developers) [Support](https://wordpress.org/support/plugin/broadcaster-auto-responder-for-gravity-forms/) ## Description **This is a connector plugin for [Broadcaster](https://getbroadcaster.com), a paid SaaS platform for business WhatsApp management. It is not a free WhatsApp integration; it requires an active Broadcaster account.** If you do not have one, this plugin will not do anything useful on its own. If you _are_ a Broadcaster customer using Gravity Forms on a WordPress site, this plugin forwards each form submission into your Broadcaster inbox as an incoming contact message, and can optionally trigger an approved WhatsApp template reply ( in business hours, out of business hours, or both: Broadcaster picks based on your company’s business-hours settings). **Full setup and configuration documentation:** [getbroadcaster.com/docs/gravity-forms-addon](https://getbroadcaster.com/docs/gravity-forms-addon) #### What it does * For each form you opt in to, the submission becomes an incoming contact message in Broadcaster, attributed to the form so support staff know where the contact came from. * Each submission can trigger one optional template auto-response: either a single template that always fires, or two templates (in-hours / out-of-hours), and Broadcaster picks based on your company’s configured business hours. * A dedicated **WhatsApp Recipient** custom field (under _Advanced Fields_ in the form editor) captures the contact’s phone number in a single input, validates the format inline before form submission, and prevents the submitter from accidentally collecting a typo’d number that Broadcaster would later silently fail to deliver to. Or use any standard Gravity Forms field as the recipient mapping for backward compatibility. * Phone or WhatsApp username (or both) are mapped from form fields you nominate. * Standard Gravity Forms merge tags work in the message body and in template placeholder values. * Standard Gravity Forms conditional logic decides whether a feed runs for a given submission. * Failures never block the form: a Broadcaster outage doesn’t stop the user’s submission, the email notification, or the confirmation page. When Broadcaster declines a recipient as undeliverable, the failure is surfaced inline on the Gravity Forms entry detail so site administrators can see what didn’t deliver and why. #### What it does *not* do * It does **not** give you WhatsApp messaging. It just hands form submissions to your Broadcaster account, which is what actually talks to WhatsApp Business. * It does **not** create a Broadcaster account, manage templates, or open the WhatsApp customer-service window. Templates must already exist and be approved on the Broadcaster side. * It does **not** do full phone-number validation. The **WhatsApp Recipient** field does normalise national-format numbers to international format (`+44…`, `+1…`) using the country you configure, and catches obvious typos before submit, but Broadcaster’s own normalization rules remain the source of truth. For other field types, submit numbers in international format where possible. #### Ownership and affiliation This plugin, the **Broadcaster** service it connects to ([getbroadcaster.com](https://getbroadcaster.com)), the **Fullworks** brand ([fullworks.net](https://fullworks.net)) and **Fullworks Plugins** ([fullworksplugins.com](https://fullworksplugins.com)) are all owned and operated by Fullworks Digital Ltd, a company registered in England and Wales, the same company that publishes this plugin on WordPress.org under the account “fullworks”. Broadcaster is our own product, not a third party’s. “Gravity Forms” is a trademark of Rocketgenius, Inc. and “WhatsApp” is a trademark of Meta Platforms, Inc. This plugin is an independent, unofficial add-on and uses those names only to describe what it is compatible with. ### Privacy This plugin is a connector to **Broadcaster** ([getbroadcaster.com](https://getbroadcaster.com)), a third-party WhatsApp business-messaging platform operated by Fullworks Digital Ltd. When you connect a Gravity Form to Broadcaster and a submission is received, the plugin transmits the following personal data from that submission to Broadcaster’s servers: * The contact’s phone number and/or WhatsApp username (as mapped in the feed). * The submitter’s name, when a name field is mapped. * The message text and any form-field values you include in the message body or template placeholders. * A form identifier and source label used to attribute the message inside Broadcaster. Data is sent **only** for forms you have explicitly connected to Broadcaster, and** only** when a Broadcaster API key is configured. No data is sent before then, and the plugin contacts no other external service. Nothing is collected for the plugin’s own purposes: no telemetry, analytics, or tracking. Broadcaster processes the data it receives under its own [Privacy Policy](https://getbroadcaster.com/privacy) and [Terms of Use](https://getbroadcaster.com/terms). The plugin also registers suggested disclosure text under **Settings Privacy** in WordPress, so you can fold this data flow into your site’s own privacy policy. ### Source Code This plugin ships its complete, unminified PHP, JavaScript and CSS source inside the distributed package; there is no separate obfuscation or minification build step, so the code you run is exactly the code you can read. For support or to report an issue, use the plugin’s support forum on WordPress.org. ### Troubleshooting #### “Broadcaster API key is not configured” admin notice Configure the API key under _Forms Settings Broadcaster_. #### “Gravity Forms is not active” admin notice Install and activate Gravity Forms. This plugin needs Gravity Forms to do anything; it sits idle until Gravity Forms is present. #### “✗ Not connected. Broadcaster rejected the API key (HTTP 401/403).” The saved key is wrong, has been revoked, or belongs to a different company. Re- issue an API key in Broadcaster under _Settings API Keys_, paste it on the WP side, save. #### “✗ Not connected. Broadcaster URL responded but the messages endpoint was not found (HTTP 404).” Only relevant on dev/staging/local. The URL points at a host that isn’t a Broadcaster instance, or one that hasn’t been updated to a build that includes the contact-form API. Production sites use `https://getbroadcaster.com` and won’t see this. #### “✗ Not connected. Cannot reach Broadcaster: …” The site can’t open an HTTPS connection to Broadcaster. Check outbound firewall / proxy / DNS on the WordPress server. #### Form submission shows no error but nothing arrives in Broadcaster Open _Forms Settings Logging_ and enable the **Broadcaster Auto Responder for Gravity Forms** logger at _Log all messages_. Submit again, then download the log. Common causes: * Conditional logic on the feed didn’t match the submission. * Neither phone nor WhatsApp username was mapped, or the mapped field was empty. * Template name in feed config doesn’t match an approved Broadcaster template. * Required template variable missing from placeholder map. * Phone/username normalization mismatch: contact gets created on the Broadcaster side but template send fails because the recipient can’t be resolved. #### “Broadcaster rejected the message (HTTP 422). The form id field must be a string.” Indicates a plugin/Broadcaster version mismatch. Upgrade this plugin to 1.0.0 or later. ## Installation #### Prerequisites 1. An active **Broadcaster** account at [getbroadcaster.com](https://getbroadcaster.com). 2. **Gravity Forms** installed and active on your WordPress site (Gravity Forms is a third-party paid plugin). #### Install the plugin 1. Upload the plugin to `/wp-content/plugins/broadcaster-auto-responder-for-gravity- forms` (or install the zip via _Plugins Add New Upload Plugin_) and activate it. 2. In WordPress admin, go to **Forms Settings Broadcaster**. 3. Paste your Broadcaster API key (generate one in Broadcaster under _Settings API Keys_) and click **Save Settings**. 4. After save, the page shows **✓ Connected** if Broadcaster accepts the key, or ** ✗ Not connected** with a reason if it does not. The Broadcaster site URL is hardcoded to `https://getbroadcaster.com` on production sites. On dev/staging/local environments (sites where `WP_ENVIRONMENT_TYPE` is not` production`) the URL field is editable so you can point at a non-prod Broadcaster instance. #### Configure a form 1. Edit the Gravity Form you want to forward. 2. Open **Settings Broadcaster** in the form editor and click **Add New** to create a feed. 3. Set the feed name and (optionally) a **Source label**, which is what shows in Broadcaster chat bubbles to identify where the message came from. Defaults to the form’s title. 4. Map at least one of: 5. * **Phone field**: the form field that holds the contact’s phone number. * **WhatsApp username field**: for contacts who send via WhatsApp username/BSUID rather than phone. 6. Optionally map a **Submitter name field**. 7. Write the **Message text** the contact’s submission becomes inside Broadcaster. Gravity Forms merge tags work, for example `{Message:5}` or `{Name (First):1.3}`. 8. Optionally fill the **In-hours template name** (the _internal_ name of an approved Broadcaster template). If only this field is set, Broadcaster uses it at all times. If both this and the out-of-hours template name are set, Broadcaster picks by company business hours. If neither is set, no auto-response is sent. 9. Optionally fill the **In-hours template placeholders** as comma-separated `key: value` pairs. Values may include merge tags. Example: text_1:{Message:5},client_first_name:{ Name (First):1.3} 10. Repeat for **Out-of-hours template name** and **Out-of-hours template placeholders** if you want a different reply outside business hours. 11. (Optional) Use Gravity Forms’ standard **Conditional logic** to run the feed only when chosen form fields match. 12. Save the feed. Submit the form to test; the message should appear in Broadcaster within seconds, and the auto-response (if configured) should send shortly after. ## FAQ ### Do I need a paid Broadcaster account? Yes. This plugin is a connector for [Broadcaster](https://getbroadcaster.com), a paid SaaS platform for business WhatsApp management. Without an active Broadcaster account and an API key, the plugin has nothing to talk to. ### How can I evaluate this before committing? Broadcaster offers a **30-day free trial**, so you can test the whole flow end to end. The trial itself is free; the only possible cost is Meta’s own WhatsApp charges if you send template messages, which Meta bills you for directly (that billing relationship is between you and Meta, not this plugin). 1. Sign up at [getbroadcaster.com/pricing](https://getbroadcaster.com/pricing). 2. In Broadcaster, connect your own Meta (WhatsApp Business) account and a phone number to send from. 3. In Broadcaster, create an API key (_Settings API Keys_). 4. In WordPress, go to _Forms Settings Broadcaster_ and paste the API key. A green** ✓ Connected** confirms it. 5. Edit a Gravity Form and add the **WhatsApp Recipient** field (under _Advanced Fields_) to capture the contact’s number. 6. Open the form’s _Settings Broadcaster_ and add a feed mapping that field, plus your message text and (optionally) a template. Submit the form, and the message should appear in your Broadcaster inbox within seconds. ### Is this an official Gravity Forms add-on? No. This plugin is built on the public Gravity Forms Feed Add-On Framework but is published independently by Fullworks. Gravity Forms itself must be installed separately. ### Will Broadcaster outages break my forms? No. If the Broadcaster API is unreachable or rejects the request, the form submission still completes; Gravity Forms confirmations and notification emails proceed as normal. The failed dispatch is recorded under _Forms Settings Logging_ (when GF logging is enabled). ### Where do template names come from? You enter the **internal name** of an approved Broadcaster template (the slug-style name visible inside Broadcaster’s template management UI, not the display title). Templates must already exist and be approved on the Broadcaster side; this plugin doesn’t create or sync templates. ### What’s the difference between “Message text” and the templates? The **Message text** is the inbound contact message stored in Broadcaster, which is what your support staff sees in the chat thread. The **template** is the optional outbound auto-response sent to the contact’s WhatsApp. Broadcaster won’t send a message to a recipient whose WhatsApp customer-service window isn’t open _unless_ a template is used; that’s why this plugin offers template fields. ### Can I run multiple feeds on one form? Yes. Add as many feeds as you like per form. Use Gravity Forms’ standard conditional logic to send different submissions to different Broadcaster destinations. ### How do I match by WhatsApp username only (no phone)? Map the **WhatsApp username field** but leave the phone field unmapped. Broadcaster will store/match by username. Note that auto-response template delivery currently requires a phone or BSUID Broadcaster can resolve; username-only contacts can be created but template delivery may report `recipient_not_deliverable` until that resolves. ### What’s the WhatsApp Recipient field, and should I use it instead of a stock phone field? It’s a custom field type this plugin adds, found under _Advanced Fields_ in the Gravity Forms editor. It accepts a phone number in any reasonable format (with or without a country code), validates inline before submit so the visitor sees typos as a “Please enter a valid phone number” error and corrects them on the spot, and pre-cleans the value to international format so Broadcaster receives clean data. Use it on new forms and on any form where silent lead-drops have been a problem. Existing forms with stock Gravity Forms phone / text fields continue to work exactly as before; the new field is opt-in. (A future release will also accept WhatsApp usernames in the same field, once Meta enables that feature publicly.) ### Phone numbers in national format don’t match my existing contacts. Why? Broadcaster’s phone normalization needs to know which country to interpret a national- format number against. The **WhatsApp Recipient** field handles this for you: configure a default country under _Forms Settings Broadcaster Phone normalisation_, and the field assumes that country whenever a submitter types a national-format number( and overrides it whenever they type an explicit `+` international prefix). For stock Gravity Forms phone fields, configure the field to require international format, or rely on Broadcaster’s company-level default phone country. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Broadcaster Auto Responder for Gravity Forms” is open source software. The following people have contributed to this plugin. Contributors * [ fullworks ](https://profiles.wordpress.org/fullworks/) * [ Alan Fuller ](https://profiles.wordpress.org/alanfuller/) [Translate “Broadcaster Auto Responder for Gravity Forms” into your language.](https://translate.wordpress.org/projects/wp-plugins/broadcaster-auto-responder-for-gravity-forms) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/broadcaster-auto-responder-for-gravity-forms/), check out the [SVN repository](https://plugins.svn.wordpress.org/broadcaster-auto-responder-for-gravity-forms/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/broadcaster-auto-responder-for-gravity-forms/) by [RSS](https://plugins.trac.wordpress.org/log/broadcaster-auto-responder-for-gravity-forms/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.1.5 Wp Org release #### 1.1.4 * **WordPress.org compliance.** All admin JavaScript and CSS is now loaded through the standard WordPress enqueue functions instead of being printed inline. The form-editor helper script and the connection-status styling load via `wp_enqueue_script`/` wp_enqueue_style`; there is no change to how the plugin behaves. * **Hardening.** Auto-response and recipient-rejection details returned by Broadcaster are now passed through `sanitize_text_field()` before being written to a Gravity Forms entry note. * **WhatsApp Recipient field** now uses natural tab order rather than emitting its own tabindex attribute. On the vast majority of forms this is invisible; forms that set a custom Gravity Forms tab-index start will see this field follow normal source order. * **Maintenance:** removed the placeholder Screenshots section from the readme until images are bundled, deleted an unused internal helper, and updated the development environment dependency. #### 1.1.3 * **Privacy disclosure.** Added a Privacy section to this readme spelling out exactly what submission data is sent to Broadcaster, and registered suggested privacy- policy text in WordPress (_Settings Privacy_) so site owners can disclose the data flow to their visitors. The plugin’s data handling is unchanged; this surfaces what already happens. * **Admin notices are now scoped.** The “Gravity Forms not active” and “API key not configured” warnings now appear only on the Plugins list, Dashboard, and Gravity Forms admin pages (where they’re actionable) instead of on every admin screen. Both still disappear automatically once resolved. * **Maintenance:** pointed the plugin / add-on link at the documentation page (` getbroadcaster.com/docs/gravity-forms-addon`), inlined output escaping in the form-editor inline script, and documented why the Gravity Forms tab-index attribute is emitted as-is. No functional change. #### 1.1.2 * **The auto-response outcome is now visible in Gravity Forms.** After Broadcaster accepts a submission, the plugin reads the `auto_response` block from the response and writes a clearer entry note: “sent auto-response (`