examples

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

Time-Based Automation Strategies

Delay Nodes enable time-based strategies when used thoughtfully.

Strategy 1: Cooling-off periods

Use delays to:

• Give users time to read content
• Avoid overwhelming them
• Make automation feel human

Example:

• Send info message
• Delay 5 minutes
• Ask a follow-up question

Strategy 2: Sequenced messaging

(Daily news updates or scheduled daily content delivery)

Delays can be used to build safe, time-based message sequences that deliver content gradually while staying within Instagram’s 24-hour messaging rules.

Example sequence structure

A typical daily sequence can be designed as follows:

Message 1
→ Delay (up to 22 hours)
→ Message 2 (includes a Button or Quick Reply)
→ Delay (up to 22 hours) placed on the Button or Quick Reply handler
→ Message 3

Why this structure works

• The first delay keeps the flow safely within the 24-hour window
• The Button or Quick Reply in Message 2 encourages user interaction
• User interaction refreshes the 24-hour messaging window
• The delay placed on the button/Quick Reply handler ensures:
• • The next message is sent only after interaction
  •  If the user does not tap the Button or Quick Reply, the flow does not continue, preventing messaging outside the 24-hour window
  • The sequence can safely continue into the next day

This pattern allows you to send daily or scheduled content without breaking messaging limits.

Common use cases

• Daily news or updates
• Educational content delivered step by step
• Multi-day onboarding messages

Important reminder
Sequenced messaging should feel helpful, optional, and easy to stop.
Never force users through long sequences without interaction.