Understanding Actions

In Zaplane, a Trigger starts a workflow, but an Action is what the workflow actually does. Actions are the tasks that execute automatically when a trigger fires. For example: sending an email, creating a WordPress user, updating a WooCommerce order status, or posting a message to Slack.

In this document, you will learn:

What an action is and how it differs from a trigger.
How to add and configure actions.
The difference between single actions and multiple actions.
Using dynamic data from triggers inside actions.
Best practices for working with actions.

1. What is an Action?

An action is a task that your workflow performs. After a trigger fires, Zaplane runs all the actions you have defined in sequence.

Examples:

Create User (WordPress) – Creates a new user account.
Send Message (Slack) – Posts a message to a Slack channel.
Update Order Status (WooCommerce) – Changes the status of an order.
Add Contact (Mailchimp) – Adds a subscriber to a mailing list.

A workflow can have one action or many actions. Actions run in the order you arrange them.

2. Types of Actions

Zaplane supports hundreds of actions across different apps. Below are common categories.

a. WordPress Actions

Action Name	What it does
Create Post	Publishes a new post or page
Update Post	Modifies an existing post
Create User	Adds a new user to WordPress
Update User	Changes user details or role
Delete User	Removes a user (use carefully)
Send Email	Sends an email via wp_mail()

b. E‑commerce Actions (WooCommerce, SureCart, StoreEngine)

Action Name	What it does
Create Order	Generates a new order programmatically
Update Order Status	Changes order status (e.g., to “completed”)
Add Product to Cart	Adds an item to a user’s cart
Apply Coupon	Applies a discount coupon
Create Customer	Creates a customer record

c. CRM & Marketing Actions (FluentCRM, Mailchimp, ActiveCampaign)

Action Name	What it does
Add Subscriber	Adds a contact to a list
Remove Subscriber	Removes a contact from a list
Send Email Campaign	Triggers an email campaign
Update Contact Field	Modifies custom field values

d. Communication Actions (Slack, Discord, Telegram, WhatsApp)

Action Name	What it does
Send Message	Posts a text message to a channel or chat
Send File	Uploads a file attachment
Send Direct Message	Sends a private message to a user

e. Form Actions (Gravity Forms, Fluent Forms)

Action Name	What it does
Create Entry	Adds a new form entry
Update Entry	Modifies an existing entry

3. How to Add and Configure an Action

Step 1: Open the Action box

In your workflow, click Add Action inside the Action box (right side).

Step 2: Choose an app

Select the app you want to perform the action – e.g., WordPress, Slack, WooCommerce.

Step 3: Choose an action type

From the list, pick the specific action – e.g., “Create User”, “Send Message”.

Step 4: Configure the action fields

Each action has its own configuration fields. For example, the “Create User” action may require:

Username
Email address
Password
Role (e.g., subscriber, editor, administrator)
Display name

Step 5: Use dynamic data from the trigger

Inside any field, type @ to insert data that came from the trigger. For example:

Use the trigger’s post author email as the new user’s email.
Use the post title as the user’s display name.

This makes your actions dynamic and context‑aware.

Step 6: Save the action

Click Continue to save the action. You will see it connected to the trigger.

4. Multiple Actions in One Workflow

You can add more than one action to a single trigger. Actions run in sequence from top to bottom.

Example:

Trigger: WooCommerce → Order Completed
Action 1: Slack → Send Message (“New order #123 received”)
Action 2: FluentCRM → Add Subscriber (add customer to newsletter)
Action 3: WordPress → Create User (create an account for the customer)

To add another action, click Add Action again – it will appear below the existing one. You can drag and drop to reorder.

5. Action Error Handling

If an action fails (e.g., API timeout, invalid data), Zaplane can handle it in two ways:

Stop workflow – The workflow stops, and no further actions run.
Continue – The failed action is logged, but the next action runs anyway.

You can configure this in the action’s advanced settings.

Failing actions are recorded in the Logs section, where you can see the exact error message.

6. Testing Actions

Before activating a workflow, test each action individually or the whole flow.

Click Test Flow in the top bar.
Zaplane will ask for a sample trigger event (or use the last real event).
It will run the trigger and all actions.
Check the results – success or failure.

If an action fails during testing, adjust its configuration and test again.

7. Common Mistakes and Solutions

Problem	Possible Cause	Solution
Action doesn’t run	Action not properly saved or disabled	Ensure the action is configured and the workflow is active
Dynamic field is empty	Wrong @ variable used	Check the trigger’s output in Logs to see available data
API error (e.g., Slack)	Missing or invalid credentials	Verify your connection settings for that app
Action runs but does nothing	Field mapping incorrect (e.g., wrong email format)	Test with sample data and check the action’s logs

8. Best Practices for Actions

Use dynamic data whenever possible – Hard‑coding values limits reusability.
Name your actions (if the interface allows) so you can identify them in logs.
Add conditional logic before an action using the Condition tool – run an action only if certain criteria are met.
Test each action separately before building complex multi‑action workflows.
Check your app’s API limits – some apps restrict how many actions you can perform per minute.

Summary

Actions are the tasks that make your automation useful. Without actions, a trigger would do nothing. Zaplane gives you hundreds of ready‑to‑use actions across WordPress, WooCommerce, CRMs, forms, communication tools, and more. By mastering actions – adding, configuring, using dynamic data, and chaining multiple actions – you can build powerful, time‑saving automations.

In the next document, we will explore Tools (Condition, Filter, Delay, Iterator, Variable, HTTP Request) that you can place between triggers and actions to add logic and control.

Useful Links:

Official Zaplane Website
Previous: Understanding Triggers
Next: Using Tools (Condition, Filter, Delay, etc.)