The Storydoc connector for Claude lets you create, personalize, and manage your Storydoc presentations directly from Claude's chat interface — no switching between tools required. This article walks you through connecting Storydoc to Claude and using it to generate stories with natural language.
How the Connector Works
Once connected, you can use Claude to perform various Storydoc actions including:
Generate new stories from scratch
Create versions from existing templates
Get analytics data
List available stories
Plan story versions with dynamic variables
Step 1: Add the Storydoc Connector in Claude
Open Claude and click the + button in the chat input area. Select Add connector, then choose Browse connectors to open the connector directory.
In the search bar, type Storydoc. The Storydoc connector will appear in the results — it's listed as a Community connector. Click the + button next to it to begin the setup process.
Step 2: Generate a Storydoc API Key
Clicking the Storydoc connector will take you to the Connect to Storydoc authentication page, where you'll need to paste your Storydoc API token. If you don't have one yet, you'll need to create it inside Storydoc.
In Storydoc, go to Automations in the left sidebar and click Create an API key. Give your key a name and select its scope — you can grant access to all your stories or restrict it to a specific story. Then click Create.
Step 3: Complete the Connection
Copy your newly generated API key and return to the Claude authentication page. Paste the key into the Storydoc API token field.
You can also enter a Default sender email (optional). If set, this email address will be used as the sender for all decks you create through Claude. Leave it blank if you'd prefer to be asked each time. When you're ready, click Connect.
Once connected, you can verify the connection by going to Claude's settings, navigating to Connectors, and finding Storydoc listed there. You'll see all the available read and write tools the integration has access to, including listing templates, creating story versions, getting analytics, and more.
Step 4: Create a Story Using Natural Language
With the connector active, return to Claude's main chat interface. You can now ask Claude to create Storydoc presentations using plain language — no need for specific commands or syntax.
For example, type something like: "Create a Storydoc proposal for Nike." Claude will process your request and automatically check your available templates and stories to find the best match.
Claude will reply with a recommended template and may suggest alternatives if other templates are a better fit. It will also list any dynamic variables the template requires — such as a recipient's first name and last name — before creating the deck.
Step 5: Provide Dynamic Variables
If your template uses dynamic variables (like first_name and last_name), Claude will ask you to supply them before generating the deck. Simply reply with the values in a natural way.
For example: "Anna - First name, Novak - Last name." Claude will map your input to the correct template fields and proceed to create the personalized story.
Step 6: Access Your Newly Created Story
Once the story is generated, Claude will confirm the creation and provide two direct links:
Share link — the live URL you can send to your recipient
Editor link — opens the story directly in Storydoc for further edits
Click the share link to view your finished, personalized presentation exactly as your recipient will see it.
More Things You Can Do with Storydoc in Claude
Once connected, the integration goes far beyond creating a single deck. Here are some useful things to try:
Generate from scratch:"Generate a Storydoc sales deck for an AI-powered customer support platform targeting mid-market SaaS companies. Bold, confident tone."
Pull analytics:"How is the Nike proposal performing? Who viewed it and which slides got the most attention?"
Browse templates:"List my Storydoc templates and show me what fields they need."
Create multiple versions:"Use my proposal template to create three decks: one for Nike with recipient Sarah, one for Adidas with recipient Marcus, and one for Puma with recipient Lin."
Chain actions:"Create a sales deck for Acme Corp, then tell me how my last three decks have been performing."
Tips for Better Results
Be specific about audience and tone when generating from scratch — "bold pitch for enterprise CTOs" gets better results than "sales deck."
Mention the recipient by name when personalizing a template — Claude maps it to the correct variable automatically.
Select "Always allow" the first time you run a tool so future actions don't pause for approval.
Set a default sender email once during setup, and Claude will use it for every future deck.
Include your company website URL when generating from scratch so Storydoc can pull your brand colors, logo, and imagery automatically.
Troubleshooting
Storydoc doesn't appear as a connector after adding it.
Quit and reopen Claude completely (use ⌘Q on Mac, not just close the window). Connectors load on app start.
The API token connection fails.
Make sure you've generated a fresh API token in Storydoc under Automations. Older tokens may have been revoked. Generate a new one and paste it again.
Claude says it can't find my templates.
Ask Claude: "List my Storydoc templates." If the response is empty, check in Storydoc that you have at least one story in Live status with dynamic variables. Stories in Draft or Archived status are filtered out by default.
Variables aren't filled in on the created deck.
Make sure the variable names you reference match exactly what's in your template — they are case-sensitive. You can ask Claude: "Show me the variables for the [template name] template" to confirm the exact names.
Generated decks look generic and don't match my brand.
Include your company website URL in the prompt when generating from scratch. Storydoc fetches brand colors, logos, and imagery from there. Example: "Generate a sales deck for Acme. Our website is https://acme.com."
I'm hitting rate limits.
Storydoc's API allows 150 requests per minute for version-creation endpoints. If you're chaining many creations, space them out. Your plan may also have a monthly request quota — see storydoc.com/pricing for details.