Userflow is now a public app on Zapier

Zapier

Userflow the best no-code builder for building in-app user onboarding, has been integrated with Zapier for more than a year, and we are happy to announce that we just moved from beta, to being a public app.

The Userflow-Zapier Integration enables you to instantly connect Userflow with 5,000+ apps to automate your work and find productivity super powers.

Example use cases

  • Pass survey/NPS responses made in Userflow to other tools. E.g. post it on your CRM timeline, or post it in a shared Slack channel.
  • Pass events, such as when flows are completed, to other providers, such as your marketing/email automation tools.
  • Trigger workflows in a CRM/Customer Success Platform based on Userflow events or vice versa.
  • Update user details in Userflow, when the user’s info changes in another system such as your CRM.

More information

Get an Onboarding Review

The Holidays are close, and at Userflow we are already dressed up in the Userflow Xmas swag and feeling jolly and generous.

Zapier

Thus we want to give a gift to all the great SaaS companies out there. So therefore we are now offering free trial/freemium onboarding reviews until the 20th of December.

The onboarding reviews will be done by me (Esben, co-founder of Userflow) and follow a similar video style to the onboarding reviews we have done in our SaaS Onboarding Review video series. Nothing will be shared publicly, we will send the review in an email.

Want a review?

If you have a free trial or freemium, then share your website and request here. Note that your email domain needs to match your website domain.

Submit a request to get a review

Unlimited viewers for Pro and Enterprise

As an early xmas gift, we’re happy to announce that we now allow customers on Pro and Enterprise plans to add unlimited viewers (read-only team members) to their accounts.

Great onboarding is a company-wide initiative that does not only involve one team.

We already offer great integrations to bring Userflow data into other systems (e.g. CRMs and analytics tools), but we wanted to allow our customers to add other team members to Userflow to be able to keep track of surveys, onboarding progress and much more directly in the Userflow app.

This is especially valuable as we have strengthened functionality around:

We hope you will find this ability useful. Go to Settings -> Team and add your team members today.

Mixpanel cohort sync

You can now continuously sync Mixpanel cohorts to Userflow.

This way you can use Mixpanel’s more advanced conditions for targeting users that should see specific content from Userflow.

It’s super easy to set up. Check the Mixpanel integration docs.

Only start flow if not completed

A common use case is to have a recurring flow that starts periodically until the user completes it. This was possible before using a “Flow x is completed” condition. But now we’ve made it even easier with a simple checkbox:

Only if not completed

This checkbox appears if you pick either Multiple times per user or Unlimited times per user.

Control time between flows

Most Userflow customers have many flows that start automatically. But sometimes flows aren’t time-critical, and you want to avoid overwhelming the user with too many auto-started flows in quick succession.

Before, you could limit how quickly a flow was allowed to show after another flow using an Event condition such as “Flow Started exactly 0 times in the last 1 hour”. But that was neither intuitive nor that easy to maintain.

We’ve now made this a native feature in Userflow. Simply use the new At least x hours after any flow setting:

Control time between flows

The case against "Next-next-next tours"

A common pitfall in user onboarding is building what we call “Next-next-next tours”: A series of tooltips that point out stuff in your app with “Next” buttons to go to the next step. These tours are boring and unengaging, making users drop out early and not gain anything (or even worse: frustrate them!).

Instead, you should build action-based flows that drive users towards their “Aha moment”. Read more in our new Flow best practices guide.

To further combat Next-next-next tours, we’ve added a proactive detection in the flow builder that’ll warn you if a flow looks like a Next-next-next tour:

Warning about next-next-next tour

Tooltips now auto-dismiss by default if target can't be found

We’ve changed the standard behavior of when a tooltip target can’t be found. Previously, if you used our standard themes, the following message would be shown:

Warning

Going forward, the flow will auto-dismiss if the tooltip target is not found within 3 seconds.

We’re making this change in an effort to get more out of the user’s way. Only in cases where it’s absolutely necessary for the user to complete a guide, do we recommend presenting the user with the above message. In most regular onboarding flows or feature announcements, if the user does navigate away, it’s most likely that they just don’t want to continue the tour. Therefore we feel it’s better to err on the side of just dismissing the flow and let the user continue unhindered.

This change only applies if you’re using one of our standard themes. If you’re using a custom theme, the setting you had under Tooltip → Missing tooltip target behavior still applies. You can, of course, change that if you wish. Read more in our Missing tooltip target behavior guide.

Groups is now Companies

We’ve renamed our Groups feature to now be called Companies instead.

The word “group” was originally chosen because it was a broader term than “company”, meaning it could cover both companies, accounts, teams, organizations etc. - whatever term our customers may use to group multiple users belonging to the same entity together. Another reason was that popular tools used the term, too, such as Segment’s analytics.group() JavaScript API.

We’ve come to the conclusion that “groups” is a confusing term, and is often misunderstood as “segments” (which we also have).

To make the distinction crystal clear, Groups is now Companies 🤓

For now, this is solely a terminology rewording, and no actions are required of you. We’ve updated our UI and documentation use the word “company” everywhere possible. Userflow.js has not changed and still uses userflow.group(), just like the REST API has not changed and still uses endpoint URLs such as /groups and group_id for object properties.

The Product-led Stack

What tools do you actually need in a product-led stack?

Product-led Stack

Read full post