Storydoc Integration: Turn Content Agent Articles into Storydoc Presentations

Once connected, the ReddGrow content agent turns each approved article into a Storydoc presentation. Storydoc's AI builds a new live story from the article, using your website's brand colors, fonts and logo, and ReddGrow saves the link on the draft.

Unlike a CMS, Storydoc publishes a deck, not a copy of the blog post. The deck keeps the article's facts and structure but is laid out as slides.

Requirements

• A Storydoc plan that includes API access. If you can't find the API key described below, ask Storydoc to enable API access on your plan
• A user in your Storydoc workspace to act as the sender. Every generated deck is owned by this user

Get your credentials

1. Log in to Storydoc
2. Open the Integrations page
3. Go to the Automations tab
4. Copy your API key

The key acts as the user who created it and sees the same stories and folders they do. If you get authentication errors later, regenerate the key on the same page and reconnect.

Sender email: the email address of a Storydoc user in your workspace. It must belong to a user in the same workspace as the API key, or Storydoc rejects the request.

Connect in ReddGrow

1. Go to Settings → Integrations
2. Under Website publishing, find the Storydoc card and click Connect
3. Fill in the form:
   • Company website: your site's full https:// address. Storydoc takes brand colors, fonts and logo from it
   • API key: the key you copied above
   • Sender email: the Storydoc user who will own the decks
4. Click Connect Storydoc

ReddGrow checks the key with Storydoc before saving it. If another platform is already connected, ReddGrow warns you that connecting Storydoc will replace it. Only one website can be connected at a time.

How publishing behaves

• Publish creates a new live Storydoc story. Generation takes 30 to 90 seconds
• Update creates a new story with a new link. Storydoc's API can't edit an existing story, so the earlier one stays in your workspace
• Unpublish isn't available through Storydoc's API. Delete the story in Storydoc yourself
• FAQ blocks and meta description edits don't apply to presentations, so ReddGrow skips them

To change a published deck's design or wording, edit it directly in Storydoc.

Troubleshooting

Connecting fails with "API key rejected"

Check that you copied the whole key from the Automations tab and that your Storydoc plan includes API access. Regenerate the key on the Integrations page if it may be outdated.

Publishing fails with a 400 error

The sender email most likely doesn't belong to a user in the workspace that owns the API key. Use the email of an existing Storydoc user and reconnect.

Publishing fails with "too many requests"

Storydoc allows 150 generation requests per minute per organization. Wait a minute and retry.

Publishing takes a long time

Normal. Storydoc's AI runs a multi-step pipeline for each deck, so allow up to 90 seconds.

A deck uses the wrong brand colors

Brand styling is derived from the Company website you connected. Reconnect with the correct address, or adjust the design in the Storydoc editor.

---

Related: see the ReddGrow App guide for how campaigns, drafts, and the platform's automation pipeline fit together.