Resources · Make integration

Storydoc Make integrationAutomate Storydoc with Make.

Can Make create a new version of a Storydoc story for you? The Storydoc Make integration offers one action module, Create Story Version, and no trigger. This page is for sales and marketing teams who already use Storydoc: it shows how to link your account and build a first working scenario.

Try the Storydoc integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Storydoc Make integration let you automate?

The Storydoc Make integration links your Storydoc account to Make, a tool where you build a scenario (the automation you design: a chain of modules that runs on a schedule or when an app calls Make). Storydoc brings one module to that chain, Create Story Version, an action that another app or a schedule has to start.

A story version when a deal moves. Put a trigger from your CRM or form tool first, then Create Story Version. The data that arrives from the first app is mapped into the Storydoc module, so the version starts from what just happened, not from a copy and paste. Which data it accepts is not documented: Run once shows you.

A version for each row of a list. When your prospects live in a sheet, a trigger from that sheet can feed Create Story Version one row at a time. Each row travels as a bundle (one item passed from a module to the next), and each bundle becomes one run of the Storydoc action.

A version started on your own schedule. Without any other app, Make can start the scenario on its clock: a new scenario runs every 15 minutes by default, and you change that setting on the first module.

Know the limits before you start. The app has no trigger, so Storydoc cannot start a scenario by itself, and it has no Make an API Call module to reach anything beyond Create Story Version. The official documentation also warns that its content is AI generated and may contain mistakes, so check important details with Storydoc. Storydoc may also exist as an n8n node; the n8n vs Make page lays out how the two tools differ. For a guided start, see Make training, or read Make pricing before you pick a plan.

Connect

How do you connect your Storydoc account to Make?

  1. 01

    Copy your API key in Storydoc

    Open your Storydoc dashboard, click Settings, then Integrations, and open the Automations tab. The API key shows on screen: copy it. You need an active Storydoc account for this key to exist.

  2. 02

    Add the module and create the connection

    In your scenario, add the Storydoc module and click Create a connection. A connection is your Storydoc account linked to Make once, then reused by every Storydoc module. You can type a label in Connection name, which is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from Storydoc, or follow the instructions Make shows on screen, then save. The connection now appears in the module, and Make can act on your Storydoc account through it.

First scenario

Build your first scenario with Storydoc

GoalWhen a new record arrives in another app, Make runs Create Story Version in Storydoc.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add a first module. Storydoc has no trigger, so this first module comes from another app, such as your CRM or a sheet.

  2. 02

    Set up the starting app

    Search for that other app, pick its trigger, and link your account with Create a connection. Fill its fields; Make lists what it can read once the account is linked.

  3. 03

    Add Create Story Version

    Click the + on the right of the first module, search for Storydoc, and pick Create Story Version. Connect it with your API key, then map the data coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open the bubbles above each module to read the bundles it received, then check in Storydoc that the new version looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What the Storydoc module does in Make

Storydoc gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Storydoc1

Create Story Version

ActionIn the docs only

This action gives you a new version of a Storydoc story without opening Storydoc. It is the only Storydoc module in Make, so every scenario with this app ends on it or passes through it.

When to use it
place it after a trigger from another app, so a fresh event such as a new deal or a new row starts the version.
Watch out
the documentation gives no description of its fields, so run the scenario once and check the result in Storydoc before you switch it on.
Need help

Need help automating Storydoc with Make?

A person reads every message.

FAQ

Storydoc and Make: frequent questions

01Is the Storydoc Make integration free?
Yes, on the Make side. Storydoc is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. You still need an active Storydoc account, which Storydoc bills on its own terms.
02What do you need to connect Storydoc to Make?
An active Storydoc account and its API key. In Storydoc, open the dashboard, go to Settings, then Integrations, and copy the key shown in the Automations tab. In Make, add the Storydoc module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves every Storydoc module in your scenarios. If you do not have an account yet, Storydoc points to its own pricing page for the subscription.
03Does the Storydoc Make integration react in real time?
No, because Storydoc has no trigger in Make, neither scheduled nor instant. The scenario has to start elsewhere. The first option is a trigger from another app: if that app offers an instant trigger, it calls Make through a webhook as soon as something happens, and Create Story Version follows right after. The second option is the schedule of the first module, which Make checks every 15 minutes by default, or down to every minute on a paid plan.
04What if the Storydoc module you need is missing in Make?
It depends on what you need. Storydoc offers a single module in Make, Create Story Version, and no Make an API Call module, so nothing else in Storydoc can be reached from a scenario. The official documentation also flags that its text is AI generated and may contain mistakes, so confirm key details with Storydoc directly. If your case goes beyond creating a story version, check whether another app in your stack covers it, or ask the team at the agency to look at your process.
05Should you use Make or n8n for Storydoc?
It depends on the tool your team already runs. On Make, Storydoc gives you Create Story Version and nothing more, with a visual editor, a Run once test button and a Free plan to try it. The same app often has an n8n node too, so check what that node covers before you choose. There is no reason to switch tools only for Storydoc: pick the one where your other automations already live, then compare what each covers for this app.
Same platform

Other docs you might need on this stack.

Browse all integrations