Last updated: March 2026 Category: Flows
Overview
Actions are the nodes in a flow that actually do something — send a message, update a user's profile, add or remove a user from a segment, or call an external service. BeyondCart provides four action types, each designed for a specific purpose.
Prerequisites
An active or draft flow in the BeyondCart editor
Familiarity with the flow canvas (see Creating a Flow)
At least one communication channel configured for messaging actions
Step-by-Step Guide
Send Push Notification
This is the most commonly used action. It sends a push notification to the user's mobile device via Firebase Cloud Messaging.
Add a Send Push Notification node to the canvas.
Click the node to open the configuration panel.
Fill in the following fields:
Title — The notification headline. Example: "Still thinking about it?"
Body — The notification message. Example: "{{user.first_name}}, your {{trigger.product.title}} is waiting in your cart!"
Image (optional) — Upload or select an image to display in the notification.
Deep Link (optional) — A link that opens a specific screen in the app when tapped (e.g., a product page or the cart).
Action Button (optional) — A custom button label and link.
Use personalization variables to make messages dynamic. Available variables include:
{{user.first_name}}— The user's first name.{{user.last_name}}— The user's last name.{{user.email}}— The user's email.{{trigger.product.title}}— The product title from the triggering event.{{trigger.product.image_url}}— The product image URL.{{trigger.order.total}}— The order total from the triggering event.{{store.name}}— Your store name.
[Screenshot: Send Push Notification configuration panel with title, body, image, and personalization variables]
Update User
This action modifies a user's profile data. Use it to tag users, set custom properties, or update metafields.
Add an Update User node to the canvas.
Click the node and configure:
Field — Choose which user field to update (e.g., a custom tag or metafield).
Value — Set the new value. You can use static values or personalization variables.
Common use cases:
Set a "welcomed" tag after a welcome series completes.
Update a custom loyalty tier based on flow logic.
Clear a flag after a win-back campaign runs.
[Screenshot: Update User action setting a custom tag "welcome_complete" to "true"]
Manage Segment Membership
This action adds or removes a user from a static segment. It is useful for building audiences dynamically based on flow behavior.
Add a Manage Segment Membership node to the canvas.
Click the node and configure:
Segment — Select the target segment from the dropdown.
Action — Choose Add to Segment or Remove from Segment.
Common use cases:
Add users who complete a purchase to a "Converted Buyers" segment.
Remove users from a "Cart Abandoners" segment after they recover their cart.
Add users who reach a Goal to a "High Engagers" segment.
[Screenshot: Manage Segment Membership action adding user to "Post-Purchase VIPs" segment]
Send Webhook
This action sends a POST request to an external URL, letting you integrate BeyondCart flows with other tools and services.
Add a Send Webhook node to the canvas.
Click the node and configure:
URL — The endpoint to call (e.g.,
https://your-api.example.com/webhook).Headers (optional) — Custom headers such as
Authorization: Bearer {{YOUR_TOKEN_PLACEHOLDER}}.Payload — The JSON body to send. You can use personalization variables in the payload.
Common use cases:
Notify your CRM when a user reaches a milestone.
Trigger a third-party email or SMS service.
Log flow events to an analytics platform.
[Screenshot: Send Webhook configuration with URL, headers, and JSON payload fields]
Key Concepts
Personalization variables make actions dynamic. They pull real-time data from the user's profile and the triggering event.
Actions execute in order. The flow processes nodes sequentially — a user will not reach the second action until the first has completed.
Webhook failures are retried. If a webhook call fails, BeyondCart retries up to three times with exponential backoff.
Tips and Best Practices
Always personalize push notifications. Messages with the user's name and relevant product details see significantly higher tap-through rates.
Use Update User to track flow progress. Setting tags or metafields helps you build segments and conditions based on which flows a user has completed.
Combine Manage Segment with conditions. After a condition node, add users to different segments based on which branch they took.
Test webhooks with a request catcher like a tool at
https://webhook.siteduring development to verify payloads before connecting your production endpoint.
FAQ
Q: Can I send email or SMS from a flow action? A: Currently, the primary messaging action is Send Push Notification. Email and SMS actions can be achieved through the Send Webhook action by connecting to your email or SMS provider's API.
Q: What happens if a push notification fails to deliver? A: If the user's push token is invalid or expired, the notification is marked as failed. The flow continues to the next node regardless of delivery success.
Q: Can I use personalization variables in webhooks? A: Yes. All personalization variables available in push notifications are also available in webhook URLs, headers, and payloads.
Q: Is there a limit to how many actions a flow can have? A: There is no hard limit on the number of action nodes. However, keep flows readable and focused for easier maintenance.
Related Articles