Learning Lindy

Delegation: 101

In this guide, you will learn how Lindies can delegate to other Lindies to complete complex workflows.

Lindies excel at handling specialized and complex workflows, but there are cases that may require a Lindy to pass the "task" over to another Lindy to pick up the workflow and complete a new task that it's specialized in or configured to do. This is called Delegation.

The benefit of having a Lindy delegate to another is that you can select which information and context gets sent to the new Lindy, significantly decreasing the amount of tokens and context being used to complete the remainder of the workflow.

Delegation allows for more modularized Lindies, which is best practice when you want to make changes, connect disparate workflows, or have one Lindy ‘own’ a specific aspect of the workflow that may also be part of others.

You can delegate tasks to any Lindy that has an "Agent" trigger.

Delegation is best used when:

The task you want Lindy to perform reaches a point where it may require specialization.
- Example: If you have one Lindy who specializes in performing research and qualifying leads, and one Lindy who specializes in sending outreach to qualified leads, one Lindy would complete the qualification task and send the qualified lead information to your Outreach Lindy to perform the outreach.

The context being passed to each step of your Lindy's workflow is quite large.
- Example: One Lindy researches a topic across web pages, then passes only the relevant information to a Newsletter Drafter Lindy. This second Lindy drafts and emails the newsletter using just the essential content, without the excess context from the research process.

A good way to think about delegation is like a webhook. One Lindy performs a task until a given point or information is retrieved, then that information gets sent to another Lindy (just like using a webhook), and you can define what information is received by the second Lindy.

Setting up delegation is fairly simple and will take no longer than 2 minutes to build.

Let's get started!

Setting Up Delegation: A Practical Example

In this guide, we'll create two Lindys that work together:

A Lead City Locator Lindy
A Lead Outreacher Lindy

Here's what they'll do:

The Lead City Locator takes leads sent by the user and finds their city using the Search the Internet action.

Once it enriches the lead and finds their city name, it sends the information to the Lead Outreacher Lindy.

The Lead Outreacher Lindy then sends the lead a personalized email, pitching a new office space located in their city.

Let's create these Lindys step by step.

Creating the Lead Outreacher Lindy

First, we'll create the Lindy that will receive the delegated task. We’ll start by giving this Lindy the ability to receive messages.

Note: We're setting up this Lindy first, even though it will receive delegated tasks.

In the next section, we'll create the delegating Lindy and configure these fields. You can return to this step later to refine your prompts once both Lindies are set up.

Give Lindy the Ability to Receive Messages

Create a new Lindy by clicking the plus sign beside Lindies.

Click "Start from scratch" to create a new Lindy.

Click "Select Trigger" and select the Agent Message Received trigger.

Triggers are events that “wake up” a Lindy. Examples include time-based triggers (e.g., every weekday at 9 am) or event-based triggers (e.g., when you receive an email).

A single Lindy can have multiple triggers, either managing different workflows, or acting as entry points into the same workflow.

Configure the Workflow.

Now that Lindy can receive a message from another Lindy, we can configure the rest of the workflow.

To do this, add a Send Email action.

In the Send Email action, we can use prompts that refer to information the Lindy will receive from another Lindy.

Creating the Lead City Locator Lindy

Now, let's create the Lindy that will do the initial work and then delegate.

Create a New Lindy

Follow the same steps as before to create a new Lindy.

This time, select a trigger that initiates when you send a lead (e.g., Chat Message Received).

Configure the Workflow

Add a People Data Labs Find Person by Email action to find the lead's full name using their email address.

Add a Web Browser Search the Internet action to find the lead's city.

Configuring the Agent Send Message

For the final step, we need to add the Agent Send Message action.

Click Add Step after the last action in your workflow and select Perform an Action.

Search for the Agent Send Message action.

Under the Lindy field, you will see a dropdown menu of all your existing Lindy’s that are configured to receive messages from an Agent Message Received trigger.

Select your Lead Outreacher Lindy.

In the Text field, specify the exact information you want to send to your Lead Outreacher Lindy (lead name, email address, and city).

Let’s See How it Works

In the example below, I sent my Lead City Locator a lead email address.

Lindy used People Data Labs to find the contact by email address and get the lead's full name.

Then Lindy performed a web search to find their city of residence.

After that, Lindy delegated to my Lead Outreacher Lindy, sending the lead name, email address and city name.

The Lead Outreacher Lindy received the lead information and used this information to craft an outreach email.

You can see the trigger was a message from the Lead City Locator Lindy and the email was sent, referencing the information received in the message.

‍

Guides

Tips For Reducing Costs

Meeting Notetaker with Follow-Up Email‍