ShopMagic for Gravity Forms - WordPress Plugin

How to Set Up ShopMagic for Gravity Forms and Run Automations After Form Submission

ShopMagic for Gravity Forms is not meant to replace the form itself. Its role is to connect Gravity Forms submissions with ShopMagic's automated emails and actions. This guide focuses on the practical side: what to check before installation, how to enable the integration, how to choose the Gravity Forms Submission event, which placeholders to use in your email, where to review the queue and results, and how to troubleshoot cases where the email was not sent or form data was not inserted correctly.

This guide is intended for a WooCommerce site owner, marketer, or webmaster who already understands why a form belongs on the site, but wants to turn a lead, questionnaire, consultation request, or expression of interest into a managed communication flow. That is why this article does not repeat the product page copy and does not cover purchasing instructions. The focus is on how to test everything safely with a staging form, avoid interfering with live store emails, and avoid promising more to the user than the automation actually does.

This article covers only confirmed functionality: the add-on introduces a form submission event, provides access to four form placeholders, works when ShopMagic PRO and the official Gravity Forms plugin are installed, and lets you verify submission results through the queue, the Outcomes log, and email deliverability checks. If your version of the interface looks slightly different, keep the same sequence in mind: form and test entry first, then event, action, placeholders, publishing, and log review.

What Problem the Gravity Forms and ShopMagic Integration Solves

Gravity Forms collects data through a form: name, email, selected service, comment, file, consent, request type, or any other field structure. ShopMagic works as an automation system inside WordPress and WooCommerce: it uses an event, an optional filter, and an action. ShopMagic for Gravity Forms connects those two layers so that submitting a specific form can become the starting point for an email, a sequence of emails, or another supported automation.

The simplest scenario is an email sent after a lead form submission. A user leaves their email in Gravity Forms, and ShopMagic sends a welcome message, confirmation, resource bundle, or internal team notification. A more useful scenario appears on a WooCommerce site: the form might capture interest in a product, a pre-purchase consultation request, a sizing request, a wholesale quote inquiry, or post-order feedback. After that form is submitted, the store owner gets more than just an entry in Gravity Forms - they get a managed communication flow with a queue, log, and email template.

The main value of the add-on is not "one more email," but moving form data into ShopMagic logic. Using placeholders, you can insert the sender's email, entry ID, form ID, and a field value into the email subject, body, or recipient field. That saves you from writing the same replies manually or keeping a separate spreadsheet when all you need is a basic post-form follow-up.

Where This Approach Works Especially Well

This integration works best when the form is the beginning of the funnel rather than the final step. For example, a store sells complex products and offers a "Get a consultation" form; a school accepts course applications; a service business collects quote requests; a B2B store provides a form for wholesale buyers; or an ecommerce site wants to send a quick reference guide after a product-matching form. In those cases, the post-form email should be predictable, contain the actual request data, and be traceable through a log instead of disappearing inside standard Gravity Forms notifications.

If all you need is one standard admin notification, Gravity Forms alone may be enough. ShopMagic for Gravity Forms makes sense when you want ShopMagic rules, a centralized log of marketing emails, access to additional add-ons, integration with WooCommerce scenarios, or one consistent approach to store automation.

Who ShopMagic for Gravity Forms Is For, and When Another Approach Makes More Sense

This plugin is a good fit for site owners who already use Gravity Forms and ShopMagic, or who plan to manage communication directly from WordPress without relying on a separate external service. It is especially useful if ShopMagic already handles WooCommerce emails: post-purchase follow-ups, reminders, team notifications, or personalized messages. In that case, the form becomes one more entry point into the same system.

A strong use case is a site where the form collects an email address and enough context for the next message. For example, a demo request, a discount inquiry for a business customer, a pre-consultation questionnaire, a post-purchase feedback form, a back-in-stock interest form, or an event registration form. If you need to send one email to the visitor, notify a manager, and then verify whether the message was actually sent, ShopMagic offers clearer control than scattered notification settings.

When the Add-on May Be Unnecessary

Do not install ShopMagic for Gravity Forms just because your site has a form. If standard Gravity Forms notifications already cover your needs, you do not use WooCommerce, you do not have ShopMagic PRO, and you have no plans for email sequences, the add-on adds another dependency without much benefit. It also does not replace a CRM if you need full deal tracking, manager statuses, calling, tasks, and communication history outside WordPress.

For more advanced email marketing with large lists, off-site behavioral segmentation, A/B testing, and a dedicated sending infrastructure, a CRM or email platform is a better fit. ShopMagic for Gravity Forms is stronger in local WordPress and WooCommerce scenarios where a form launches a specific action, not as a universal marketing hub.

Practical rule: if the form only needs to notify the site administrator, start with Gravity Forms. If a form submission should become part of WooCommerce automation, placeholder-driven emails, a queue, and a verifiable log, then ShopMagic for Gravity Forms is the more logical choice.

What to Check Before Installation and First Launch

Before installation, it is important to verify more than just the plugin files. This integration depends on three layers: WordPress/WooCommerce, ShopMagic, and Gravity Forms. If any one of those layers is set up carelessly, the automation may look correct in the editor but still fail after a real form submission.

Required Dependencies

This add-on requires ShopMagic PRO and the official Gravity Forms plugin. The core version of ShopMagic is available in the WordPress.org directory, but the Gravity Forms integration is part of the PRO add-ons. WooCommerce is not always the center of the form workflow, but ShopMagic is positioned as a WooCommerce marketing automation tool, so on ecommerce sites it makes sense to confirm up front that WooCommerce is running properly, store emails are being sent, and the administrator knows where to manage automations.

• Make sure the main ShopMagic plugin is installed and active, and that the automations section is visible in the admin panel.
• Make sure the official Gravity Forms plugin is active and that you have at least one test form with an email field.
• Make sure ShopMagic for Gravity Forms is activated as an add-on and that Gravity Forms Submission appears in the available ShopMagic events afterward.
• Test a regular WordPress or WooCommerce email so you do not confuse a delivery issue with an automation issue.
• Create a test page with the form and do not launch your first workflow on an important public-facing form without testing.

What Kind of Form Works Best for Testing

It is better to start with a short form than a large production questionnaire: name, email, request subject, and comment. That makes it easier to see which field is passed into a placeholder, where the Gravity Forms entry appears, and which address should receive the email. After a successful test, you can move the workflow to a form with conditional logic, multiple pages, or extra fields.

If the form is already being used on the site, review its confirmations and notifications in Gravity Forms. ShopMagic should not accidentally duplicate the same message. For example, if Gravity Forms already sends the user a confirmation and ShopMagic adds a welcome email, those two messages should serve different purposes. The first confirms that the request was received, and the second moves the user to the next step.

Email, Cron, and the Queue

ShopMagic uses a queue and Outcomes logs, so when there is a sending issue, you need to inspect more than just the form. If emails are not going out, the cause may be WP-Cron, the Action Scheduler queue, SMTP configuration, a spam filter, or a problem in the action itself. Before your first launch, it is worth checking basic deliverability: whether the site can send a standard email, whether the sender uses a domain-based address, and whether outbound mail is restricted by the hosting environment.

Installation and Initial Verification of the Form Event

Installation is just the standard process of enabling WordPress plugins, but the first verification step should be more careful. Your goal is to confirm that the add-on is not merely active, but that it actually added a new event to the ShopMagic editor and can see the correct Gravity Forms form in the dropdown.

General Enablement Order

1. Install and activate the main ShopMagic plugin if it is not already installed.
2. Confirm that Gravity Forms is active and that the form opens in the editor.
3. Activate ShopMagic for Gravity Forms from the available add-ons.
4. Open the ShopMagic automation editor and create a new automation.
5. Open the event selector and find Gravity Forms Submission.
6. Select the specific form from the list, save the draft, and do not publish the automation until the action is configured.

If the event does not appear, first check whether the add-on is active. Then confirm that the main ShopMagic plugin and Gravity Forms are enabled. Do not start troubleshooting email settings if the event is missing from the interface: at this stage, the issue exists before any email is sent.

What You Should See After Activation

With a correct installation, you should see the Gravity Forms Submission event and be able to choose a form. On the product page and in the documentation, the developer specifically notes that installing the add-on adds a new event and new placeholders, and that the add-on itself does not require a separate settings page. That detail matters: the real configuration work happens inside a specific ShopMagic automation, not on a standalone add-on settings screen.

After selecting the form, do not rush to publish the workflow. Give the automation a clear name, such as GF - Consultation Request - Welcome Email. That will make log filtering, automation exports, and support conversations much easier later. Vague names like Form email quickly become a problem once the site has several forms and several email flows.

Configuring the Automation After a Gravity Forms Submission

The most useful part of the setup starts after you select the event. In ShopMagic, an automation is built from an event, a filter, and an action. With ShopMagic for Gravity Forms, the event is the submission of the selected form. The filter is optional, and the action will most often be an email. The action determines who receives the message, what the subject line will be, which form data appears in the content, and how the user understands the next step.

Selecting the Event and Form

In the event field, choose Gravity Forms Submission, then select the form. If your site has many forms with similar names, rename them before building the automation. In the interface, it is much easier to work with clear names like Consultation Request, Wholesale Inquiry, or Product Fit Quiz than with something like Contact form 1.

One important check: submit a test entry through the exact form selected in the event. If the automation is attached to a different form, the email will not fire even if the fields look identical. This is a common logic error on sites where forms are duplicated across multiple pages.

Recipient Address

For a visitor email, you will usually need the email address from the form entry. ShopMagic for Gravity Forms documentation points to the {{ form.entry_email }} placeholder. It makes sense to use it in the To field if the form really includes the sender's email and the add-on correctly recognizes that field. For an internal notification to a manager, you can use a fixed address and display the form data in the subject line and body of the email.

Do not use a personal Gmail address or a random external address as the site's sender address. For better deliverability, use a domain-based sender address together with an SMTP plugin or a transactional email service if the hosting platform does a poor job sending WordPress mail. In its article about sending problems, ShopMagic specifically recommends checking standard WooCommerce emails, Outcomes statuses, spam signals, SMTP, and the Action Scheduler queue.

Subject Line, Heading, and Message

The email subject should be clear to both the user and the administrator. For the user, a phrase like "We received your request" works well; for the team, "New request from consultation form" is more useful. If the form supports several scenarios, you can add a field value to the subject using {{ form.entry_field }}, but do it carefully: if the field is long or contains free-form text, the subject line can become unreadable.

In the email body, use placeholders to reinforce context. For example, you can display the entry number {{ form.entry_id }} for internal lookup, or the form identifier {{ form.form_id }} if your team works with multiple forms. For the user, the entry number only helps if you actually use it in support. Do not add technical data to an email simply because it is available.

When You Need a Filter

A filter in ShopMagic is optional. If you want to send one email after every submission of the selected form, do not add a filter without a reason. The more conditions you introduce, the harder troubleshooting becomes. Filters are useful when the scenario depends on customer data, order data, user roles, order totals, statuses, or other ShopMagic-driven information. For Gravity Forms fields, do not invent filtering logic if the source does not confirm the operator you need or if the field is not visible in the interface.

In a typical setup, it is best to start with a simple rule: one event, one form, one action. Once that is working, you can add a second automation for the manager, introduce a delay through Delayed Actions, or export data through the Google Sheets add-on if those tools are available on your site.

Quick setup takeaway: first make sure the email is sent after a test form submission without any filter. Only after that should you make the workflow more complex with conditions, delays, and additional actions.

Form Placeholders: How to Keep Submission Data From Getting Lost in the Email

Placeholders are where ShopMagic for Gravity Forms becomes a real product integration rather than just a trigger. The add-on documentation lists four new placeholders: {{ form.entry_email }}, {{ form.entry_field }}, {{ form.entry_id }}, and {{ form.form_id }}. These let you connect the email to the Gravity Forms entry and use form data directly inside the automation.

How to Use Each Placeholder

This table does not mean you should insert all four values into every email. A user-facing email should stay short and clear. An internal notification can be more technical because the manager benefits from the entry ID, form name, and quick request context.

A Typical Placeholder Error

The most frustrating issue is when the email is sent, but the raw placeholder remains instead of real form data. That may mean the wrong placeholder was selected, the automation was triggered by the wrong event, the form field was empty, or you are trying to use data the add-on does not expose in that form. In that case, do not start rewriting the email blindly. First open the Gravity Forms entry, confirm that the field is filled in, then review Outcomes in ShopMagic, and only after that edit the email.

For long free-form user messages, it is usually a bad idea to build the email subject line from the full field value. It is better to use a short subject or request type and keep the full comment in the body of the email. That makes the message easier to read and prevents email clients from cutting off the important context.

Practical Example: Email After a Consultation Form in WooCommerce

Let us walk through a scenario that clearly shows why this add-on matters. A WooCommerce site sells products that often require a consultation before purchase. On the product page or on a separate page, there is a Gravity Forms form called "Find the Right Solution." After the form is submitted, the user should receive a polished confirmation email, and the manager should receive an internal notification with the request details and the entry number.

Goal

Create an automation that runs after a specific Gravity Forms form is submitted, sends an email to the submitter's address, and helps the team locate the entry. This is not a mass mailing and not a complex CRM funnel. It is a fast, verifiable follow-up email that reduces manual work and makes the site's response predictable.

Preparation

• Create or select a form with a required email field, a name field, and a "What do you need help choosing?" field.
• Add the form to a test page using a standard Gravity Forms method: block, insert button, or shortcode.
• Verify that a submission creates an entry under Forms and that the email address is visible in the entry.
• Disable the duplicate user notification in Gravity Forms, or change its purpose so the user does not receive two nearly identical emails.

Steps in ShopMagic

1. Create a new automation and name it clearly enough to show which form triggers it.
2. In the event, select Gravity Forms Submission and the specific consultation form.
3. In the action, choose email sending.
4. In the To field, insert {{ form.entry_email }} if your test confirms that this placeholder returns the submitter's address.
5. Write a short confirmation subject line without technical details.
6. In the email body, explain the next step: when the team will reply, which details have already been received, and what the user should do if they made a mistake in the form.
7. Add {{ form.entry_id }} either to an internal copy or to a separate automation for the manager so the request can be found quickly in Gravity Forms.
8. Publish the automation only after submitting a test entry.

Verification

After publishing, submit the form using a test address on your own domain or in a mailbox you control. Check four places: the Gravity Forms entry, the ShopMagic queue, Outcomes in ShopMagic, and the actual inbox. If the entry exists but there is no email in Outcomes, the issue is in the event or the automation. If Outcomes shows success but the message is not in the inbox, check spam, SMTP, and the domain-based sender address. If the email arrives but the form data is empty, go back to the placeholders and the test entry.

A Detail People Often Miss

The consultation form may be embedded on several pages. If it matters which page the request came from, add a hidden field or another standard Gravity Forms mechanism for passing page context ahead of time. Do not invent that information inside the ShopMagic email if the form itself does not collect it. The automation can only insert values that are available to the event and its placeholders.

How to Verify the Result: Form Entry, Queue, Outcomes, and Deliverability

Verification should be part of setup, not an emergency step after a customer complains. ShopMagic has an Outcomes log and queue, Gravity Forms has Entries, and email delivery has its own separate signals. If you check everything in the right order, the root cause is much easier to identify.

Verification Order After a Test Submission

1. Open Gravity Forms Entries and make sure the test entry was created.
2. Check that the entry belongs to the same form selected in the ShopMagic event.
3. Open the ShopMagic log and locate the automation by name.
4. Review the status in Outcomes: success, failure, or no event.
5. If the action is delayed or sitting in the queue, check Queue and Action Scheduler.
6. Open the mailbox, including the spam folder.
7. If the email was not delivered, check SMTP, the sender address, and baseline WordPress/WooCommerce mail delivery.

Do not skip the first step. If there is no Gravity Forms entry, ShopMagic should not have run. In that case, the problem is in the form itself, its embed, validation, anti-spam protection, or a page-level conflict. If the entry exists but ShopMagic does not react, inspect the event and the selected form. If ShopMagic shows success but the email is not received, then the problem is email delivery.

How to Read Outcomes

According to the ShopMagic documentation, a Success status means ShopMagic sent the email from its side. That does not always mean the message reached the inbox, because the recipient's mail server, spam filter, or a poorly configured domain sender may block it afterward. A Failure status usually means you need to inspect the detailed error message. If the error is unclear, save the error text, the automation name, the form entry ID, and the result of a regular WordPress email test.

When to Check Action Scheduler

If emails stall, are delayed, or fail to process on a low-traffic site, inspect Action Scheduler in WooCommerce. In its troubleshooting guidance, ShopMagic specifically points to WP-Cron and the task queue. On a live site, do not clear the queue or modify cron behavior without a backup and a clear understanding of the impact. First document the symptom: are there overdue tasks, does the error repeat, and does it affect only ShopMagic or all scheduled WooCommerce actions?

Use Cases That Show the Add-on's Strength Better Than a Standard Notification

To keep ShopMagic for Gravity Forms from turning into a duplicate of standard notifications, use it where you need logic after the form submission. Below are several scenarios that work especially well on WooCommerce and WordPress sites when they match your business workflow.

Inquiry Before Purchasing a Complex Product

The user selects a project type, budget, desired timeline, and leaves an email address. ShopMagic sends a confirmation email with the promised next step, while the manager receives an internal notification with the entry ID. If you also use filters or other ShopMagic add-ons, the workflow can be expanded, but even the basic version already solves the problem of manually reacting to form submissions.

Lead Magnet After Form Submission

The form collects an email in exchange for a guide, checklist, or webinar recording. After submission, ShopMagic sends an email with the material or the link. The key here is not to hide consent or overuse email: the user should clearly understand what they are signing up for. If you need a full newsletter subscription flow with segmentation, review the list and unsubscribe capabilities in your ShopMagic setup.

Internal Routing of Requests

If the form is used by sales, support, or service teams, ShopMagic can send an internal email with the request details and a link to the entry. In that kind of workflow, a polished template matters less than complete information: who submitted the form, what the topic is, which entry ID is involved, what the next step is, and where to view the original record.

Sending Data to Spreadsheets Through Another Add-on

On the ShopMagic for Gravity Forms product page, the developer mentions that form submissions can be exported to spreadsheets through the Google Sheets add-on. That is useful for reporting and operational tracking, but it does not replace email verification. If you are both sending an email and transferring data to a sheet, test the two actions separately: first the email, then the sheet, then the two together.

How to Design a Post-Form Email So It Does Not Feel Like a Random Campaign

Once the technical test is complete, there is often a temptation to add a long sales message, coupons, product links, and several blocks of benefits right away. For form-driven workflows, that is not always a good strategy. The user has just submitted information in a specific context, so the first email should continue that context rather than restart the conversation. ShopMagic for Gravity Forms gives you the trigger and the data insertion mechanism, but the quality of the workflow depends on how accurately the email matches the user's expectation.

Separate Emails for the User and the Team

The user email should be short, calm, and easy to understand. It only needs to confirm that the request was received, remind the user what they asked about, explain the next step, and provide a safe contact method in case they submitted incorrect information. The team's internal email can be more detailed: entry ID, sender email, selected topic, important form field, link to the Gravity Forms entry, or a note about who handles the request.

Do not combine those two jobs in one message. If the user sees a technical identifier, a long internal comment, or a manager-only phrase, trust goes down. If the manager receives only "New request" without the entry ID or context, the automation does not save time. It is better to create two actions or two automations than to force one email to serve everyone.

Collect the Minimum Useful Data

For the user email, a name, request topic, and next step are usually enough. For the manager, the email address, entry ID, form name, and one or two key fields are useful. If the form is large, do not copy the entire entry into the email unless there is a real reason. Large blocks of text are harder to read in a mobile mail client, and attachments or sensitive data are usually better reviewed in the Gravity Forms entry itself, where the full context is available.

A good post-form automation explains what happens next. For example: "We received your request, and a team member will review the details and reply to this email." A weak automation simply repeats the form: "Thank you, your details are..." and leaves the user with no sense of timing, responsibility, or the next step.

Test the Email as a User, Not as an Administrator

During testing, open the email on a phone and in a normal mail client. Check the subject line, sender, first line, link visibility, and the absence of raw placeholders. If the email includes a link to a product page, consultation page, or knowledge base, open it in incognito mode. Email links often break not because of ShopMagic, but because of restricted pages, the wrong domain, caching, or redirects after a site migration.

Editorial check: if the email cannot be understood without admin-panel knowledge, rewrite it. The user does not know what automation, Outcomes, or a form ID is. Those details belong to the team, not to the person who submitted the request.

Working With Multiple Forms and Copied Automations

On a small site, there is usually one contact form. On a real WooCommerce project, that quickly turns into several: pre-purchase consultation, wholesale inquiry, return request, product-matching request, event registration, partner form, and a separate support form. ShopMagic for Gravity Forms lets you select a specific form in the event, so it is worth planning for scale early.

Naming Convention

Give your forms and automations names that match in meaning. For example, a form called GF - Wholesale Inquiry and an automation called SM - GF Wholesale - User Confirmation. This convention is optional, but it makes the log much easier to navigate. When an error appears in Outcomes, the name alone immediately tells you which form and which email belong to that workflow.

If you duplicate a Gravity Forms form, rename it immediately and confirm that the automation is attached to the new form rather than the original one. When copying automations in ShopMagic, also review the event and form selection. The most common mistake in projects like this is a well-written email published on the wrong event.

Separate Automations Instead of One Large Rule

It is sometimes tempting to build one automation that handles every form. For ShopMagic for Gravity Forms, that approach is usually worse than a set of smaller workflows. Different forms imply different expectations: a wholesale inquiry needs a response-time email, a return form needs process instructions, and a consultation form needs a confirmation and follow-up questions from the manager. If you force everything into one email, it either becomes too generic or starts filling up with unnecessary conditions.

Split workflows by purpose. One flow, one form, one primary email. If different teams need to be notified, add a separate action or a separate automation. This approach is easier to test, export, disable, and explain to a new site administrator.

What to Do Before Migrating to Another Site

ShopMagic documentation notes that automations can be imported and exported as JSON, but when moving them between stores, you need to watch ShopMagic versions and active add-ons carefully. For Gravity Forms workflows, add one more check: the matching forms and fields must exist on the new site. If the form ID is different, the automation may require manual review after import.

Before migration, create a short checklist: form name, purpose, email field, which placeholders are used, which actions are sent, and where to verify the result. That is not bureaucracy. It is protection against a situation where the email appears to be imported successfully but is no longer connected to the correct form.

Limitations and Careful Setup Without Unnecessary Risk

Every automation tool has a boundary. ShopMagic for Gravity Forms launches automations based on form submissions, but it does not fix bad form structure, it does not guarantee inbox placement, it does not turn WordPress into a full external CRM, and it should not be used to store sensitive data without a separate security review.

Do Not Rely on Past Submissions

ShopMagic documentation states that automations do not normally run retroactively for past events. For forms, the takeaway is simple: if a user submitted the form before the automation was published, the new automation should not automatically process that older entry. Plan the launch in advance and test the workflow before important leads start coming in.

Do Not Turn Placeholders Into a Data Dump

Placeholders help personalize the email, but they should not be used to dump everything into the message. If the form collects long messages, internal comments, files, or sensitive details, first decide who should receive that information. A user email often needs only a confirmation and the next step, not a full copy of the submitted questionnaire.

Do Not Overcomplicate the First Workflow With Filters

Filters and additional add-ons are useful when the core workflow is already stable. If you enable the form event, a complex filter, a delay, several actions, and a new SMTP setup all at once, it becomes hard to tell where the failure actually is. Start with the smallest working workflow and expand it one change at a time.

Respect the Boundary Between Gravity Forms and ShopMagic

Gravity Forms is responsible for form creation, validation, entry storage, and its own notifications. ShopMagic is responsible for automation after the event. If the form does not submit, do not start by looking in ShopMagic. If the form submits and the entry exists but the email is not sent, then move on to ShopMagic, the queue, and mail delivery. That boundary saves time and reduces the chance of breaking a form that is already working.

When ShopMagic for Gravity Forms Is the Right Choice

ShopMagic for Gravity Forms is worth using when a form submission needs to launch a clear, trackable communication flow inside WordPress and WooCommerce. It is especially useful when the site already uses ShopMagic, the forms are built in Gravity Forms, and the team needs events, placeholders, a queue, and Outcomes instead of scattered manual emails.

Before launching it on a live form, follow a short path: test form, Gravity Forms Submission event, one email action, then verification of Entries, Outcomes, and actual delivery. After that, add more workflows as needed: a manager email, a delay, spreadsheet export, or more advanced segmentation if it is truly necessary.

If this guide makes it clear that the product fits your site, you can download the latest version of ShopMagic for Gravity Forms and test it with a staging form. Do not start with the most important lead form on the site: first prove that the integration sees the correct form, inserts the email properly, and records the result in the log.