Every workflow in Zaplane starts with a Trigger. A trigger is the event that causes your automation to run. For example: a post is published, an order is completed, a form is submitted – these are all triggers.
In this document, you will learn:
- What a trigger is and why it matters.
- How to select and configure a trigger.
- Different types of triggers (WordPress, WooCommerce, forms, etc.).
- Using dynamic data and filters.
1. What is a Trigger?
A trigger is an event listener. It stays active and waits for a specific occurrence. When that occurrence happens, the trigger wakes up and tells the rest of the workflow (actions or tools) to run.
Examples:
- Trigger: WordPress → Post Published
What it does: When someone publishes a new post, this trigger activates. - Trigger: WooCommerce → Order Completed
What it does: When an order is completed, the trigger starts the workflow.
No workflow can start without a trigger. Every workflow must have exactly one trigger.
2. Types of Triggers
Zaplane offers hundreds of triggers across dozens of apps. Below are some important categories.
a. WordPress Core Triggers
|
Trigger Name |
When it fires |
|
Post Published |
A new post is published |
|
Post Updated |
An existing post is updated |
|
User Registered |
A new user registers |
|
User Login |
A user logs in |
|
Comment Added |
A new comment is added |
[Screenshot: WordPress trigger list showing “Post Published”, “Post Updated”, etc.]
b. E‑commerce Triggers (WooCommerce, SureCart, StoreEngine)
|
Trigger Name |
Description |
|
Order Completed |
An order is successfully completed |
|
Order Status Changed |
Order status changes (e.g., pending → completed) |
|
Product Added to Cart |
A product is added to the cart |
|
Stock Low |
Product stock falls below a threshold |
c. Form Triggers (Gravity Forms, Contact Form 7, WPForms)
|
Trigger Name |
Description |
|
Form Submitted |
Any form is submitted |
|
Entry Created |
A new form entry is created |
d. Membership & LMS Triggers (MemberPress, LearnDash)
|
Trigger Name |
Description |
|
Membership Activated |
A membership plan is activated |
|
Course Completed |
A user completes a course |
Other apps like Slack, Telegram, Zoom, and FluentCRM also have their own triggers.
3. How to Select and Configure a Trigger
Adding a trigger in Zaplane’s visual builder is very easy.
Step 1: Click on the Trigger box
In the workflow editor, click the Select an app button inside the Trigger box (left side).
Step 2: Choose an app
Select the app whose event you want to use – e.g., WordPress, WooCommerce, Fluent Forms.
Step 3: Choose a trigger type
From the list, pick the needed trigger, e.g., “Post Published” or “Order Completed”.
Step 4: Configure filters and conditions
Now decide under which specific circumstances the trigger should fire. This is where you narrow down the trigger using filters.
Example for “Post Published” trigger:
- Only posts in the “blog” category.
- Only posts by a specific author.
- Only if the post title contains a certain word.
If you add no filters, the trigger will fire every time any post is published.
Step 5: Use dynamic data
Inside the configuration panel, type @ to access data coming from the trigger. For example:
- Post title
- Author email
- Post content
These values can later be used in actions.
Step 6: Save the trigger
Click Continue to save your trigger.
4. Relationship Between Triggers and Tools
An Action usually comes right after the trigger. But you can also insert Tools (Condition, Filter, Delay, Iterator, Variable, HTTP Request) between the trigger and the action.
Example workflow:
- Trigger: WordPress → Post Published
- Condition tool: If post category is “news”, proceed.
- Delay tool: Wait 5 minutes.
- Action: Slack → Send Message
The trigger starts the entire workflow.
5. Testing a Trigger
To check if your trigger works correctly, click the Test Flow button. During testing, Zaplane will ask you to provide a sample event (e.g., a dummy post ID). If the test succeeds, you will see the output data from the trigger.
6. Common Mistakes and Solutions
|
Problem |
Possible Cause |
Solution |
|
Trigger never fires |
Filters are too strict |
Review filters; avoid overly narrow conditions |
|
Dynamic data not working |
@ used incorrectly |
Ensure the data actually comes from the trigger |
|
Test gives an error |
Invalid test data |
Use a real example (e.g., an existing post ID) |
7. Best Practices
- Apply necessary filters only – You don’t need to trigger on every post. Filter only the posts that require automation.
- Give triggers clear names – Helps when you have multiple workflows.
- Check the Logs – The Logs section shows detailed execution history, including whether your trigger fired.
- One trigger can have multiple actions – All actions connected to a trigger will run sequentially.
Summar
The trigger is the heart of every Zaplane workflow. Without it, no automation can start. By selecting and configuring triggers correctly, your workflows become more precise and efficient.
In the previous document “Create Your First Workflow”, you used a basic trigger (Post Published) to build a workflow. Now, with this deeper understanding of triggers, you can create more complex automations.
Useful Links:
- Official Zaplane Website
- Need help? Check the “Help” section inside your dashboard.
Next Document: Using Multiple Actions & Tools – Coming soon.