Learning Lindy

Step by Step Onboarding

Step-by-Step Onboarding enables you to easily onboard others to a Lindy template. Instead of requiring the users of your Lindy template to navigate a complex flow editor, build a simple form-style onboarding that allows your template users to easily configure and start using the Lindy!

Creating a Step by Step Onboarding
Form actions
Lindy configuration actions
The Step by Step Onboarding experience
Best practices
Example: Onboarding the Meeting Notetaker
Example using Copyable Content: Onboarding for the Meeting Scheduler
Example using Configure Embed, Configure Knowledge Base, and Configure Step: Onboarding for the Website Customer Support Bot

Creating a Step by Step Onboarding:

This is the high-level process of creating a Step by Step Onboarding:

Figure out what input you need to collect from your users in order to configure the Lindy template. Figure out what output you would need to show to your users in order for them to be able to use the template.
1. For example, for the Meeting Notetaker Template, you will need to collect the calendar that Lindy should use since it’s a required field. You might also want to collect input for the ‘Restrict by attendee type’ field if you want your template users to be able to configure that field in your onboarding.
2. For example, for the Meeting Scheduler Template, you will need to output the user’s Lindy Mail address that they can cc to their email threads to enable Lindy to schedule their meetings.
Build the onboarding flow in the flow editor with the Form Actions and the Lindy Configuration Actions.
1. The Form Actions enable you to show information to your users as well as collect input. The Lindy Configuration Actions allow you to collect input from your users while configuring a step in the template. All Step by Step Onboardings will start with an Onboarding trigger from the Lindy Configuration Actions, which are located under Lindy Utilities.
2. Note, user authorizations are automatically collected at the beginning of onboarding. You do not need to collect user auths as an onboarding step.
Test the onboarding flow. Click test in the upper right corner, select the onboarding trigger, and make changes if necessary.
Share

Form actions

The Form Actions enable you to show information to your users as well as collect input. These are the different form actions you can add to your onboarding:

Show Multiple-Choice - Shows a multiple choice question to your users and collects input
Show Copyable Content - Shows a piece of text ready to copy
Show Info Step - Shows information to your templates users
Show Text Input - Shows a question to your users and collects long or short text input
Show Copyable Embed Code - Shows the code snippet of a Lindy embed to copy

Each step has an ‘illustration’ field. If no file is uploaded, there will be a default illustration.

Lindy configuration actions

The Lindy Configuration Actions allow you to collect input from your users while configuring a step in the template. These are located within Lindy Utilities in the action modal. These actions include:

Collect User Input to Configure Step - Collects input from a user for a specific field and uses the values to update the configuration of the fields in a step. Cannot configure AI Agents or condition steps.
Configure Step - Collects input from a user for a step and updates the configuration of any step. Use Configure Step over Collect User Input to Configure Step if there are multiple fields in a step that you want to configure. Also a catch all for any steps not configurable by Collect User Input to Configure Step.
Configure Lindy Embed - Configures the Lindy embed trigger node.
Configure Knowledge Base - Collects data sources for a knowledge base node
Get User Info - Gets a user’s information, including their Name, Email, Time Zone, and Lindy Mail Suffix. For Step by Step Onboardings we primarily need this action for the Lindy Mail Suffix for some templates.

The Step by Step Onboarding experience:

Users who click out of a Step by Step onboarding without completing it will land on the Flow Editor for the template. They will be able to resume onboarding.
Users who finish a Step by Step Onboarding will be redirected to the Task View for the Lindy they just configured.
- To make sure this is a harmonious experience, we encourage you to add a Message Received trigger to your template with a greeting message that introduces your user to the Lindy.

Best practices:

Here are some tips to make sure your step by step onboarding is a harmonious experience:

Start with an Info Step introducing your user to the Lindy that they will be onboarded to and what it does.
In the last step of your onboarding, let the user know that the Lindy can be configured further in the Flow Editor. This lets the user know how they can further customize their Lindy.
Add a Message Received trigger to your template with a greeting message that introduces your user to the Lindy. After completing onboarding, users will be directed to the Task View and will be able to see this greeting message.
If it doesn’t make sense to add a Message Received trigger, let your users know that they can view their tasks in the Task View.
If the Lindy consists of only a Message Received trigger and an agent state, onboarding is not really needed. Instead, consider using a Show Info step to tell the user how to use the Lindy.
When thinking of inputs and outputs, consider what is required for the user to configure to ensure the Lindy can run, and critical steps that the user might want to configure.

Example: Onboarding for the Meeting Notetaker

Let’s walk through this example of building a Step by Step Onboarding for the Meeting Notetaker template.

We need to figure out what input we want to collect from our template users in order to configure the Meeting Notetaker. In this case, from the Calendar Event Started step, we need the user to configure the Calendar. Note, all user authentications are automatically configured.

Now, we need to build the onboarding flow in the flow editor with the Form Actions and the Lindy Configuration Actions.
1. All Step by Step Onboardings will start with an Onboarding trigger from the Lindy Configuration Actions, which are located under Lindy Utilities.

Lets add a Show Info step to let the template user know what this template does.

Now we need to enable the template user to configure the Calendar Event Started step that we identified in step 1. We will use the Collect user input to configure step action. Enter the question you want to ask, a description, and which step and field you want to configure.

Since thats the only step we wanted the user to configure, we are going to end the onboarding here. Lets add another Show Info step to tell the user what this Lindy does, and instruct them to go to the flow editor to configure it further.

This is the final onboarding flow:

Save and test your Step by Step Onboarding.
Share your template! Now anyone who uses the template you made will go through its Step by Step Onboarding so they can easily configure the template. They will not be able to see the onboarding flow in their template’s Flow Editor.

Example 1: Onboarding for the Meeting Scheduler

Lets walk through this example of building a Step by Step Onboarding for the Meeting Scheduler.

We need to figure out what input we want to collect from our template users in order to configure the Meeting Scheduler. In this case, going through the template steps we see that there are no fields that are required for configuration other than the user authorizations. Let's say we want to make sure the user configures the Schedule Event step to add a Zoom Link.

We also need to figure out what output you would need to show to your users in order for them to be able to use the template. For this template, we need to output the user’s Lindy Mail address that they can cc to their email threads to enable Lindy to schedule their meetings.

‍

Now, we need to build the onboarding flow in the flow editor with the Form Actions and the Lindy Configuration Actions.
1. All Step by Step Onboardings will start with an Onboarding trigger from the Lindy Configuration Actions, which are located under Lindy Utilities.

Lets add a Show Info step to let the template user know what this template does.

Now we need to enable the template user to configure the Schedule Event step that we identified in step 1. We will use the Collect user input to configure step action. Enter the question you want to ask, a description, and which step and field you want to configure.

Now, we need to show the user the meeting scheduler Lindy Mail email that they can cc to their email threads. We need to add 2 actions:
1. One is Get User Info which gets a user’s information, including their Name, Email, Time Zone, and Lindy Mail Suffix. This action will help us collect the Lindy Mail Suffix.
2. We also need to show the Lindy Mail suffix to the user and we need the user to be able to copy it, so we need the Show Copyable Content action. In the Copyable Field, configure the Lindy Mail Suffix output from the Get User Info step. Don’t forget a title and a description for the step!

Since that’s all we want to collect and show the user, we are going to end the onboarding here. Let's add another Show Info step to tell the user what this Lindy does, and instruct them to go to the flow editor to configure it further.

This is the final onboarding flow:

Save and test your Step by Step Onboarding.
Share your template! Now anyone that uses the template you made will go through its Step by Step Onboarding so they can easily configure the template. They will not be able to see the onboarding flow in their template’s Flow Editor.

‍

Example 2: Onboarding for the Website Customer Support Bot

Lets walk through this example of building a Step by Step Onboarding for the Website Customer Support Bot.

We need to figure out what input we want to collect from our template users in order to configure the Website Customer Support bot.
1. In this case, we see that the user needs to configure the Knowledge Base. We might also want the user to configure the embed. We might also want the user to define when the support message should be escalated.

We also need to figure out what output you would need to show to your users in order for them to be able to use the template. In this case, we need to show the embed code to the user to embed in their app.

Now, we need to build the onboarding flow in the flow editor with the Form Actions and the Lindy Configuration Actions.

All Step by Step Onboardings will start with an Onboarding trigger from the Lindy Configuration Actions, which are located under Lindy Utilities.

Lets add a Show Info step to let the template user know what this template does

Now we need to enable the template user to configure the Knowledge Base that we identified in step 1. We will use the Configure Knowledge Base action. Add a title, description, and choose the knowledge base step.

Now we need to enable the template user to configure the embed that we identified in step 1. We will use the Configure Lindy Embed action. Add a title, description, and choose the embed step.

Now, we need to enable the template user to define when to escalate the support request. Since this isn’t something we can do with Collect User Input to Configure Step (can’t configure AI agent or condition nodes), we will use the Configure Step action. Add a title, description, and select the condition step to configure. The Configure Step action allows you to configure all the fields in the step. You can toggle the fields you want to configure on if you want the user to configure it, or off if you don’t. Toggle the fields you don’t want the user to configure off in the ‘Fields to Configure’ section.

Lastly, we need to show the embed code to the user and instruct them on how to use it. We will use the Show Copyable Lindy Embed Code action. Add a title, description, and choose the embed step.

This is the final onboarding flow:

Save and test your Step by Step Onboarding
Share your template! Now anyone that uses the template you made will go through its Step by Step Onboarding so they can easily configure the template. They will not be able to see the onboarding flow in their template’s Flow Editor.

‍

Guides

Sales Meeting Assistant

Building a Slackbot: 101

Getting Started With Lindy: 101

Web Monitoring

Disseminate Meeting Insights

Calling any API