Skip to main content

How to Automate Storydoc with lemlist

By connecting lemlist with Storydoc, you can automatically generate a personalized Storydoc when someone engages with your outreach, then store the Storydoc link back in your CRM so reps can follow up with the right asset.

Jack avatar
Written by Jack
Updated over a week ago

Why automate Storydoc with lemlist

This workflow is useful when you want to respond to real buying signals, for example:

  • Create a personalized deck when a prospect replies to an email

  • Create a follow-up deck when someone engages with an outreach step (send, reply, bounce, unsubscribe, LinkedIn activity, phone call end)

  • Keep your CRM updated with a Storydoc link your team can send immediately

Automation works through Zapier. For setup instructions, refer to the article How to Connect Storydoc with Zapier.

Valid lemlist triggers you can use

These triggers are available in lemlist’s Zapier integration:

  1. New Activity
    Triggers when an activity occurs (for example: email sent, replied, bounced, unsubscribed, LinkedIn profile visited, phone call ended).

  2. Unsubscribed Recipient
    Triggers when a recipient unsubscribes.

For Storydoc creation, New Activity is the primary trigger because it can represent a reply or other engagement that indicates intent.

Step-by-step: Create a Storydoc when someone engages in lemlist

Before you start

Make sure you have:

  • A Storydoc workspace with automations enabled

  • A Zapier account

  • A lemlist workspace connected to Zapier (lemlist uses a team ID and API key for the Zapier connection)

  • A Storydoc template prepared with Dynamic Variables (for example: {{first_name}}, {{company_name}})

1) Create a Zap and select your lemlist trigger

  1. In Zapier, click Create Zap.

  2. Choose lemlist as the trigger app.

  3. Select the trigger event New Activity.

  4. In the trigger setup:

    • Select the relevant Campaign (if applicable).

    • Use Event Type to focus on the signal you care about (for example, a reply).

  5. Test the trigger to pull a sample activity from lemlist.

2) Create a personalized Storydoc version

  1. Add an Action step and select Storydoc.

  2. Choose the action that creates a new version from an existing Storydoc template.

  3. Map lemlist data from the activity to your Storydoc Dynamic Variables, such as:

    • First name

    • Last name

    • Email

    • Company name (if available in your lemlist lead data)

Result: Zapier generates a new Storydoc version and returns a unique link.

3) Store the Storydoc link back in your CRM

This is the most important part for day-to-day use. Your CRM becomes the source of truth for the generated Storydoc.

  1. Add another Action step and select your CRM (for example, Pipedrive, HubSpot, Close).

  2. Use a Find step (if needed) to locate the right person or deal by email.

  3. Use an Update step to write the Storydoc link into a dedicated field, such as:

    • Storydoc link

    • Proposal deck URL

    • Personalized deck

Optional: Update lemlist lead data for campaign personalization

If you want to keep the Storydoc link inside lemlist as well (for example, to use it in later steps or templates), lemlist supports actions like:

  • Update Lead From Campaign (includes a Custom Variables field you can populate)

  • Add Lead to Campaign

  • Remove Lead From Campaign

If you do this, treat it as optional. For most teams, the CRM write-back is the most valuable place to store and share Storydoc links.

Did this answer your question?