Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form below and we will reply as soon as possible.

  • Appcues Certifications & Training
  • Integration Hub
  • Contact Us
  • Docs home
  • Workflows
  • Use Cases

Create a Workflow to follow up on expansion signals

Learn how to create a Workflow that spots upgrade opportunities—like when someone hits a limit or tries a premium feature—and helps you follow up while they’re still interested.

Updated at April 14th, 2025

Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form with the details about the help content you'd like to see.

  • Installation & Developers
    Installing Appcues Web Installing Appcues Mobile API & Data Troubleshooting Extras
  • Web Experiences
    Building Web Experiences Targeting Studio Customization & Styling Use Cases Troubleshooting FAQ
  • Mobile Experiences
    Installation & Overview Building Mobile Experiences Mobile Analytics & Integrations Troubleshooting
  • Workflows
    Building & Configuration Use Cases Workflow Analytics and Integrations
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Best Practices Use Cases Pro Tips Product-led Growth
  • Integrations
    Integration Documents Use Cases Extras
  • System Status
    System Status & Incidents
+ More

Table of Contents

Build Guide Step 1. Track expansion signals Step 2. Create a new Workflow Step 3. Set start criteria Step 4. Add an in-app upgrade message Step 5. Add a delay + email follow-up Step 6. Add a goal Step 7. Set finish criteria Step 8. Publish Workflow

Build Guide


In this article, you’ll learn how to:

  • Track key expansion signals
  • Create a Workflow from scratch
  • Trigger messages based on real user behavior
  • Personalize messages based on what users did
  • Set a goal to track upgrades or engagement
  • Finish and manage re-enrollment

Step 1. Track expansion signals

First, track the behaviors that signal a user might be ready for more. These could include:

  • Hitting a usage limit
  • Interacting with a gated or premium feature
  • Visiting a pricing or upgrade page
  • Attempting an action that’s only available on a higher-tier plan

Make sure these are tracked as custom events or feature flags (e.g., hit_usage_limit, clicked_upgrade_feature, etc.).

Step 2. Create a new Workflow

In the Workflows tab, click Create Workflow and name it something like “Upgrade Follow-Up” or “Expansion Workflow.”

Step 3. Set start criteria

Click the Start node and configure:

  • Audience: All users, or a segment based on your plan tiers or usage
  • Trigger: One of the events you set up in Step 1 (e.g., hit_usage_limit)
  • Trigger timing: Immediately, so the message hits while interest is high

Step 4. Add an in-app upgrade message

Create an in-app message via Pin or Flow to help drive forward your conversion messaging.
Use this message to:

  • Call out the specific feature or limit they hit
  • Explain the value of upgrading
  • Include a clear CTA (e.g., “See plans,” “Talk to sales,” or “Unlock this feature”)

💡 Tailor the copy with personalization tokens or usage-based language (e.g., “You’ve reached your 100-item limit—time to upgrade?”)

Step 5. Add a delay + email follow-up

Not everyone will act in the moment—so follow up.

 

  • Add a Time delay: 2–3 days
  • Then add an Email node with similar messaging, or a bit more detail about your plans or benefits
  • Include a deep link to the feature or plan page to make it easy to act

Step 6. Add a goal

Add a Goal to track whether the user took action. Good goal events might be:

  • upgraded_plan
  • contacted_sales
  • viewed_pricing_page

This will help you track how often your nudges actually turn into conversions.

Step 7. Set finish criteria

Click the Finish node to set how users exit the Workflow.

  • Exit when: Goal is reached, or they finish the last step
  • Timeout threshold: 7–14 days works well for this type of follow-up
  • Re-enrollment: Enable this so users can re-enter if they hit another upgrade opportunity later

Step 8. Publish Workflow

Once everything’s in place, hit Publish—and let Workflows handle the follow-up.

👏 Done! You’ve now got a smart, behavior-based system for identifying and acting on expansion opportunities—without needing to chase users manually.
 

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Send Appcues Survey Response to Google Sheets Using Webhooks
  • Send NPS Scores and Feedback as a Single Message in Slack through Zapier
  • Create a Workflow to send renewal email messages
Appcues logo

Product

Why Appcues How it works Integrations Security Pricing What's new

Use cases

Appcues Integration Hub User Onboarding Software Feature Adoption Software NPS & Surveys Announcements Insights Mobile Adoption

Company

About
Careers

Support

Developer Docs Contact

Resources

The Appcues Blog Product Adoption Academy GoodUX Case studies Webinar Series Made with Appcues Appcues University

Follow us

Facebook icon Twitter icon grey Linkedin icon Instagram icon
© 2022 Appcues. All rights reserved.
Security Terms of Service Privacy Policy

Knowledge Base Software powered by Helpjuice

Expand