Action Node

Action Node Overview

You use the Action Node to:

• Add or remove Tags
• Set, update, or clear Fields
• Prepare user data for later conditions and personalization

Action Nodes are essential for:

• Segmentation
• Lead qualification
• Tracking progress
• Preventing repeated actions

What are Tags and Fields in Elpidan

Before using the Action Node, it is helpful to understand what tags and fields are.

Tags are simple labels used to group and segment users based on status, behavior, interests, or actions. Fields are used to store actual user data, such as name, email, phone number, score, or any other value you want to save for later use in your flows.

👉If you want to create and manage your tags, go to the Tags Menu.
👉If you want to review the available fields or create additional custom fields, go to the Custom Fields Menu

How the Action Node works

Basic behavior:

1. The flow reaches the Action Node
2. Defined actions are executed immediately
3. The flow continues to the next connected node

The Action Node executes silently. Users do not see anything unless you follow it with an Instagram Node.

Managing Tags (Add / Remove)

Tags represent boolean state — a user either has a tag or does not.

Add / Remove Tag

Segment your contacts effectively using Tags to deliver targeted and personalized content.

Common examples:

• Add tag lead
• Add tag contest_participant
• Add tag follow_required_shown
• Remove tag “new_lead” and add tag “qualified lead”

This keeps your segmentation clean and accurate.

Best practices for tags

• Use consistent naming (snake_case or kebab-case)
• Use tags to represent state, not values
• Avoid creating too many overlapping tags
• Document tag purpose for your team

Managing Fields (Set / update / Clear)

Fields store values, not just state.
The Action Node allows you to manage fields directly.

 Set / Update

Use Set / update Field to:

• Save a fixed value
• Increase or decrease the previous values
• Override previous values intentionally

Good use cases for setting Fields with Action Nodes

Fields are best used for numeric, cumulative, or measurable data that may change over time.

Field Types You Can Manage with Action Nodes

You can set, update, or clear all types of custom fields (Internal Fields & User-defined fields)

Example 1: Storing total purchase amount

You can use a Number Field to store the total value of purchases made by a user.

Example:

• Field name: total_purchase_amount
• Action: Add the value of the current purchase to this field

This allows you to:

• Track customer value over time
• Create Conditions based on spending level
• Personalize offers for high-value users

Example 2: Storing a user’s contest score

You can use a Number Field to store a user’s contest score.

Example:

• Field name: contest_score
• • For each correct answer: Add the question’s score value to this field using an Action Node

This enables:

• Fair scoring across multiple questions
• Ranking users based on total score
• Rewarding users based on performance

Updating fields dynamically

Fields can be updated based on:

• Previous user input
• Flow context
• Business logic

Example:

• Increase purchase_count

Clearing fields

Use Clear Field when:

• Data is no longer relevant
• You want to reset a process
• You are restarting a qualification flow

Example:

• Clear field temp_answer
• Clear field campaign_code 

Combine Action Nodes with Condition node

Action Nodes are most powerful when paired with logic.

• Condition → Action → Next step

This ensures actions only run when appropriate.

Example pattern 1: Smart follow invitation with combined conditions

Scenario:

You want to invite a user to follow your Instagram account only when it makes sense, while ensuring that each user receives a follow invitation no more than four times in total across all flows, to avoid spamming and maintain a positive user experience.

Condition setup

This pattern uses two sequential Condition Nodes instead of a single combined condition.

Condition 1: Check follower status
First, use a Condition Node to check whether the user is a follower.

• If the user is a follower → skip the follow invitation and continue the flow.
• If the user is NOT a follower → continue to the next condition.

Condition 2: Check follow invite count
If the user is not a follower, use a second Condition Node to check the number of previous follow invitations.

• follow_invite_count is less than 4 → invite the user to follow the account.
• follow_invite_count is 4 or more → skip the follow invitation and continue the flow.

This ensures that only non-followers who haven’t exceeded the invite limit receive a follow request.

Result

• Only non-followers receive follow invitations
• Each user is invited no more than four times
• Follow prompts feel natural, respectful, and intentional
• Automation stays compliant with Instagram limits

Example pattern 2: Counting join invitation attempts

Scenario

You want to invite users to join your Instagram channel; while making sure the same user is not invited too many times.

Setup

Use a Number Field to store how many times the user has received a join invitation.

Example:

• Field name: insta_channel_invite_count
• Each time the user is invited Increase this field by 1 using an Action Node

Flow logic

• Use a Condition Node to check whether insta_channel_invite_count is below your defined limit
• If the condition is met (green handler):
• • Increase insta_channel_invite_count by 1
  • Send the channel invitation
• If the condition is not met (red handler):
• • Skip the invitation
  • Continue the flow without sending another invite

Result

This approach helps you:

• Avoid repeatedly inviting the same user
• Apply clear limits using Conditions
• Design smarter and more respectful invitation flows 

Note: Test flows with real users
Before publishing:
Verify tags are added/removed correctly
Check field values in Contacts
Confirm conditions react as expected