Why automate Storydoc with Mailchimp
This workflow is useful when you want to:
Create a personalized Storydoc when someone subscribes to your audience
Generate a Storydoc for high-intent subscribers based on engagement (opens, segment entry)
Send internal alerts to sales when a subscriber shows intent, with a ready-to-share Storydoc link
Valid Mailchimp triggers you can use
These triggers exist in Mailchimp’s Zapier integration:
New Subscriber
Triggers when a new subscriber is added to an audience.New or Updated Subscriber
Triggers when a subscriber is added or updated in an audience.New Subscriber in Segment or Tag
Triggers when a new subscriber enters a specific segment or tag.
Optional (engagement-based) trigger:
Email Opened
Triggers when a recipient opens an email in a specific campaign.
Valid Mailchimp actions you can use
These actions exist in Mailchimp’s Zapier integration:
Add/Update Subscriber (add a subscriber, or update an existing subscriber)
Add Subscriber to Tag (tag an email address within an audience)
Create Campaign (creates a campaign draft)
Send Campaign (sends a campaign to an audience, segment, or tag)
Step-by-step: Create a Storydoc from a Mailchimp trigger
Before you start
Make sure you have:
A Storydoc template prepared with Dynamic Variables (for example {{first_name}}, {{company_name}})
A Mailchimp audience and a clear tagging or segmentation approach
A destination for storing the Storydoc link (recommended: CRM field or a tracking sheet)
1) Choose a Mailchimp trigger
In Zapier, click Create Zap.
Select Mailchimp as the trigger app.
Choose one trigger:
New Subscriber for welcome/onboarding flows
New Subscriber in Segment or Tag for segment-based messaging
Email Opened for intent-based follow-up
Select the relevant Audience (and Segment/Tag if applicable).
Test the trigger to pull a sample subscriber or event.
2) Create a personalized Storydoc version
Add an Action step and select Storydoc.
Choose the action that creates a new version from a template.
Map Mailchimp fields to your Storydoc Dynamic Variables (commonly name, email, and any fields you capture into the subscriber profile).
Test the action to generate a Storydoc version and confirm you receive a link.
3) Store the Storydoc link where your team will use it
Mailchimp is great for audience management, but the most practical place to store Storydoc links is usually your system of record.
Common write-back options:
Update the lead/contact in your CRM with the Storydoc link
Add the link to a tracking sheet for marketing and sales coordination
Notify your team in Slack or email with the Storydoc link for follow-up
4) Use Mailchimp tagging to drive the next step
If you want Mailchimp to continue the journey, use tagging to route subscribers into the right flow:
Add another Mailchimp action such as Add Subscriber to Tag or Add/Update Subscriber with tags.
In Mailchimp, use tags/segments to trigger your own automation or journey steps.
Tip: Zapier’s own guidance notes that Mailchimp automations can be triggered based on tags, with Zapier applying the tag as the action.
Recommended automation workflows
Workflow 1: Welcome Storydoc for new subscribers
Trigger: New Subscriber
Action: Create Storydoc version (welcome kit, product overview, resource hub)
Write-back: Store the Storydoc link in your CRM or tracking sheet
Optional: Add a Mailchimp tag to route the subscriber into the right nurture sequence
Workflow 2: Segment-based Storydocs for different audiences
Trigger: New Subscriber in Segment or Tag
Action: Create Storydoc version using a segment-specific template
Write-back: Store the Storydoc link in your CRM or tracking sheet
Optional: Tag the subscriber for campaign routing
Workflow 3: Intent-based Storydocs for engaged subscribers
Trigger: Email Opened (specific campaign)
Action: Create Storydoc version (follow-up deck, case studies, relevant offer)
Write-back: Notify sales and store the link in CRM for fast follow-up