Try searching for WooCommerce, Shopify, Abandoned Cart, or Pricing.
32 questions — direct answers, no fluff.
Yes. WALoops supports multiple instances of the same app, so you can connect two Shopify stores. Each instance appears as a separate choice in the Trigger app and Action app dropdowns when building an automation.
In the automation builder, find the Schedule section and select "Delay". Enter a number and choose Minutes, Hours, or Days. The minimum accepted value is 1. The automation waits that long after the trigger event arrives before executing the action.
Create one automation per reminder with different Schedule settings, for example one set to Immediate, one to 1 day delay, and one to 3 days delay. A tip in the builder reads: reminders stop as soon as the order is placed. Up to 3 reminders are supported on Premium and above.
Yes. Add a condition in the Conditions section of the automation builder. Each condition row has a field picker, an operator, and a value input. You can match all conditions or any condition using the toggle that appears when more than one condition is added.
The Conditions section shows: "No fields discovered yet for this event. Trigger a test event from [app name] to populate available fields." The Add condition button only appears after at least one event field has been discovered for the chosen event.
Open the automation builder after saving the automation. The Manual test panel in the right sidebar becomes available once saved. Enter a phone number, provide a JSON sample payload, and click "Run test". Before saving, the panel shows "Save the automation first, then manual test will become available."
The sample payload is pre-filled from the automation's last real run if one exists, labeled "from this automation's last run". If no real run exists yet, it uses a generic event example labeled "generic example for this event". You can reset it with the "Reset payload" button.
The result panel shows: "The test payload didn't match this automation's Conditions, so no message was sent. (Manual tests always ignore the Schedule delay and send immediately once Conditions pass.)" No message is delivered to the phone number entered.
In the automation builder's Field mapping section, each template placeholder shown as {{1}}, {{2}}, etc. has a dropdown to pick the corresponding trigger event field such as customer name or order total. Button URL placeholders are mapped separately and labeled "Button N URL {{N}}".
Yes. In the Recipient (To) section of the automation builder, switch from Auto to Manual and enter a fixed phone number including the country code. This is useful for store-manager alerts. The number is saved with the automation, not per order.
The right-hand sidebar in the automation builder shows a live Preview panel. For WhatsApp actions it renders the template body with mapped field values substituted from the sample payload, so you can see how the message will look before saving or testing.
A warning appears in the builder: "This template is [status] on WhatsApp, messages won't send until it's approved." On the Automation Runs page a banner also warns about this. If the template is rejected, the banner says to edit the automation and pick a different approved template.
Yes. A "New template" link next to the template picker opens the template creation modal inline without leaving the builder. The newly created template is auto-selected when you save the modal, so you can continue building the automation immediately.
When the action app is Shopify, the available actions are: Cancel order, Add tag(s), Remove tag(s), Add order note, Close order, Reopen order, and Mark as paid. Cancel order requires a cancellation reason. Add and Remove tags accept comma-separated values. Close, Reopen, and Mark as paid need no extra configuration.
The five cancellation reason options are: Customer changed/cancelled, Item unavailable, Fraudulent order, Payment declined, and Other. You must select one when the Cancel order Shopify action is chosen in the automation builder.
Choose Webhook as the action app in the builder. Configure a URL, HTTP method (GET, POST, PUT, PATCH, or DELETE), data type (JSON or Form URL-encoded), and auth type (None, Basic Auth, Bearer Token, or API Key header). For GET requests, mapped fields are sent as query parameters instead of a request body.
Four auth types are available: None, Basic Auth (requires username and password), Bearer Token (requires a token), and API Key header (requires a header name and header value). You select the auth type when configuring the Webhook action app in the automation builder.
In the automation builder, choose Bot Flow as the action app and select one active Bot Flow from the dropdown. The flow starts for the trigger's phone number instead of sending a template. If no active flows exist, a message directs you to create one on the Bot Flows page first.
Yes, in two ways. The action app can be Tags, where you choose Apply tag or Remove tag and select a tag from the catalog. You can also add it as a secondary effect in the "Also do this" section alongside any main action. Tags must exist before they can be selected.
Choose Assignment as the action app in the automation builder and select an agent from the dropdown. The automation assigns the trigger's WhatsApp conversation, and its open lead if one exists, to that agent. An existing conversation for the trigger's phone number is required.
Yes. Choose Leads as the action app, enter a lead source text, and optionally add an estimated value. The automation always creates a new lead row even for a repeat customer. You can also add lead creation as a secondary effect in the "Also do this" section of any automation.
It lets you add optional secondary effects alongside the main action. The options are: Apply a tag to the customer, Create a lead, and Close the customer's open lead. Closing a lead offers two status choices: Mark as Converted or Mark as Lost. It only closes an existing lead and does not create a new one.
Yes. Each run on the Automation Runs page can be retried. If the run already succeeded, a warning appears: "This run already sent successfully, resending will deliver another message to the customer. Continue?" The same retry option is also available from the Automations History page.
Quick start shows pre-built recipe cards for your connected apps so common automations can be set up without filling in every field manually. It only shows recipes that are marked featured and whose action app is connected. Already-connected recipes are hidden. There are also multi-step Flows that create several automations at once.
A Flow in Quick start creates multiple connected automations in one go. Each Flow card shows how many steps it contains. It is different from a Bot Flow; it is a shortcut in the automation builder that sets up a series of related automations simultaneously.
When you pick an operator such as "is set" or "is not set" in a condition row, the value input is hidden and the row shows "No value needed". These operators check only whether the field has a value, so no comparison value is required.
Yes. When a condition field has historical sample values, they are shown below the condition row as "Sample values seen: ..." to help you know what to enter. This relies on values seen from past trigger events for that field.
It controls which label appears on the Orders page checklist for that automation. You can leave it on Auto-detect and WALoops will determine the stage, or you can override it manually to set a specific label such as Confirmed or Shipped.
The save button is disabled. The builder also shows: "No connected trigger apps, Connect Shopify or FlexyPe first, then create an automation." with a "Go to Apps" button that takes you to the Apps page to connect a trigger app.
In the Field mapping section, a template with an IMAGE, VIDEO, or DOCUMENT header has its own "Header Image/Video/Document" mapping row. Map it to a trigger field that contains the URL. Leaving it unset sends the template's fixed fallback URL instead.
Yes, but for carousel templates you must pick the exact products to fill each card in the automation builder. The same product list is sent every time the automation fires; there is no per-order personalization for carousel cards.
Yes. When you add more than one condition in the automation builder, a toggle appears that lets you switch between "Match ALL" (every condition must pass) and "Match ANY" (at least one condition must pass) logic before the automation fires.
Official WhatsApp Business API, Meta's own message rates, Shopify and WooCommerce automation.
✓ No credit card required ✓ 7-day free trial ✓ Cancel anytime
