Skip to main content

How to Automate Storydoc with Greenhouse

By connecting Greenhouse with Storydoc, you can automatically create personalized, candidate-facing materials at key points in the hiring process and keep the Storydoc link accessible to your recruiting team.

Jack avatar
Written by Jack
Updated over 3 weeks ago

Why automate Storydoc with Greenhouse

Automating Storydoc creation from Greenhouse allows you to:

  • Create personalized candidate materials automatically at the right hiring stages.

  • Provide candidates with consistent, role-specific information.

  • Reduce manual work for recruiters and hiring managers.

  • Keep Storydoc links connected to candidate and application records.

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


Valid Greenhouse triggers you can use

The following triggers are officially available in Greenhouse’s Zapier integration and represent standard, widely used hiring workflows.

1. New Candidate

Triggered when a new candidate profile is created in Greenhouse.

Common use case:
Automatically generate a personalized Storydoc introduction or company overview when a candidate enters your system.


2. New Application

Triggered when a candidate submits an application for a job.

Common use case:
Create a role-specific Storydoc that explains the position, team, and hiring process, and share it with the candidate early in the process.


3. New Stage Transition (Application)

Triggered when an application moves to a new stage in the hiring pipeline.

Common use cases:

  • Generate interview preparation materials when an application reaches an interview stage.

  • Create a next-steps or follow-up Storydoc after an interview stage is completed.

This trigger is tied to the application, not the candidate profile, and reflects how Greenhouse manages pipeline stages.


Creating personalized Storydocs from Greenhouse

Once a trigger is selected, Storydoc can create a new version of a chosen template using Greenhouse data such as:

  • Candidate name

  • Job title

  • Department

  • Application stage

  • Recruiter or hiring manager name

These values can be mapped to Dynamic Variables inside your Storydoc template so each candidate receives personalized content automatically.


Writing the Storydoc link back into your hiring workflow

After Storydoc creates a personalized version, the link should remain accessible to recruiters and hiring managers.

Greenhouse supports the following update actions via Zapier:

  • Update Candidate

  • Update Application

Using these actions, you can store the Storydoc URL in:

  • A custom field

  • Application notes

  • Internal comments visible to the hiring team

This ensures the Storydoc is easy to find and reuse throughout the hiring process.


Recommended automation workflows

Workflow 1: Candidate introduction materials

Trigger: New Candidate
Action: Create Storydoc version
Write-back: Update Candidate with Storydoc link

Workflow 2: Role overview on application

Trigger: New Application
Action: Create Storydoc version
Write-back: Update Application with Storydoc link

Workflow 3: Interview preparation pack

Trigger: New Stage Transition (Application)
Action: Create Storydoc version
Write-back: Update Application with Storydoc link


Did this answer your question?