Resources · Make integration

Wordbrew Make integrationAutomate Wordbrew with Make.

Can Make open and update your Wordbrew projects for you? The Wordbrew Make integration gives you 9 modules: 8 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the Wordbrew integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Wordbrew Make integration do?

The Wordbrew Make integration lets a Make scenario (the automation you build, a chain of modules) create a Wordbrew project, change it, look through its sections or call the Wordbrew API. Each module is one brick of that chain, and your Wordbrew account is linked once through a connection.

A project that opens itself. A request lands in a form or a spreadsheet you already use in Make, and Create Project turns it into a Wordbrew project without anyone copying the details by hand.

Projects that stay current. When a deadline or an owner changes in your CRM, Update Project carries that change over to Wordbrew, so the writer sees the right version.

Sections you can reuse. Search Project Sections returns the sections of a project, one bundle each, which later modules can send to a report or a shared document.

Know the limits before you start: Make itself says its Wordbrew documentation is incomplete, and no module comes with an official description. Test every module with Run once before relying on it. For anything the listed modules do not cover, Make an API Call reaches the Wordbrew API with the same connection. If you also weigh another tool, the n8n vs Make comparison sets out the criteria, and the Make pricing guide explains how operations are counted. Stuck on an error? See Make troubleshooting.

Connect

How do you connect Wordbrew to Make?

  1. 01

    Add a Wordbrew module

    Open your scenario, click the +, type Wordbrew and pick any of its modules, for example Create Project. Then click Create a connection. The same connection will serve every Wordbrew module afterward.

  2. 02

    Name and authorize it

    Give the connection a name if you plan to link more than one Wordbrew account, which keeps them apart later. Then either approve Make on the Wordbrew page that opens, or paste the key Wordbrew gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Once the connection exists, Make can list what it is able to read in your account while you fill the module, which is the quickest sign that the link works.

First scenario

Your first scenario with Wordbrew

GoalWhen a new content request arrives in another app, Make creates the matching project in Wordbrew.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Wordbrew has no trigger, so the first module comes from the app where requests arrive, such as a form tool.

  2. 02

    Set up the first module

    Pick the module of that app that spots new entries, then link its account with Create a connection. Each new request becomes a bundle: one item handed to the next module.

  3. 03

    Add Create Project

    Click the + on the right of the first module, search Wordbrew and choose Create Project. Connect your account, then map the request data from the first module into the fields Make shows.

  4. 04

    Test with Run once

    Submit a test request, then click Run once. Read the bundles each module received, and check in Wordbrew that the project really appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust it if needed, then switch the scenario on.

Modules

What each Wordbrew module does

Wordbrew gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Wordbrew1

Create Project

ActionIn the docs only

Create Project gives you a new Wordbrew project straight from a scenario, filled with the data an earlier module passed along, so nobody retypes a brief.

When to use it
a client request comes in through a form or a sales tool and should become a project the writer can open right away.
Watch out
each run creates one more project, so a test repeated with Run once leaves duplicates to delete by hand.
Wordbrew2

Make an API Call

ActionIn the docs only

Make an API Call gets you any Wordbrew endpoint the eight other modules do not reach, reusing the connection you already created instead of a separate login.

When to use it
the action you need has no dedicated module and the Wordbrew API documentation describes the request to send.
Watch out
you write the request yourself from the Wordbrew API reference, so test it with Run once on a sample project first.
Wordbrew3

Project Created

ActionIn the docs only

Its name points to projects that were just created, but Make gives no description of it and the brief lists it as an action, not a trigger. Treat its output as something to check.

When to use it
you want to explore what Wordbrew exposes about new projects before building a flow around it.
Watch out
it cannot start a scenario on its own; place it after another module and read its output with Run once.
Wordbrew4

Project Marked Done

ActionIn the docs only

Its name points to finished projects. Make documents neither its fields nor what it returns, and it is listed as an action, so confirm how it behaves before you rely on it.

When to use it
you are testing how Make can pick up the end of a writing job, for example to tell a client.
Watch out
as an action it runs only when an earlier module reaches it, so it will not react by itself when a project closes.
Wordbrew5

Project Marked For Review

ActionIn the docs only

By its name, it concerns drafts waiting for a review. There is no official description and it is listed as an action: check what it hands back before you build on it.

When to use it
an editor wants to know which drafts need a read and you are checking whether this module can feed that list.
Watch out
run it once on a test project and open the bundles, since the documentation does not say what it sends back.
Wordbrew6

Project Started

ActionIn the docs only

Its name refers to projects that have begun. Make shows no official text for it, so what it reads or changes in Wordbrew is not documented, and it is listed as an action.

When to use it
you plan to follow the start of each writing job and want to see what this module returns first.
Watch out
do not use it as the first module of a scenario; Wordbrew has no trigger, and this module does not replace one.
Wordbrew7

Project Updated

ActionIn the docs only

Its name refers to changes on a project. It is listed as an action with no description, so compare it with Update Project before deciding which one your flow needs.

When to use it
you want to check whether it reports changes made in Wordbrew, which Update Project does not do.
Watch out
nothing in the documentation confirms its output, so a Run once on a sample project is the only reliable test.
Wordbrew8

Search Project Sections

SearchIn the docs only

Search Project Sections finds the sections of a Wordbrew project for you and returns them as separate bundles, one item per section, ready for the next module.

When to use it
you need to copy the parts of a project into a report, a spreadsheet or a message for the client.
Watch out
a search can return zero, one or many bundles, so every module after it runs once per section and spends one operation each time.
Wordbrew9

Update Project

ActionIn the docs only

Update Project lets you change an existing Wordbrew project from a scenario, so a new deadline or owner set elsewhere reaches Wordbrew without a manual edit.

When to use it
a deal or a ticket changes in another tool and the linked writing project must follow.
Watch out
it acts on one project it must be able to identify, so pass it the project from an earlier module rather than a guess.
Need help

Need help automating Wordbrew with Make?

A person reads every message.

FAQ

Wordbrew and Make: common questions

01Is the Wordbrew Make integration free?
Yes. Wordbrew is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB with 512 MB of transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to 1 minute between runs and count usage in credits, which are operations, one per module per bundle. Wordbrew's own subscription is a separate matter this page does not cover.
02What do you need to connect Wordbrew to Make?
A Wordbrew account and a Make account are enough to start; the Make documentation lists no other prerequisite. Add any Wordbrew module, click Create a connection, name it if you wish, then either approve Make on the Wordbrew page or paste the key Wordbrew provides, and click Save. Make also warns that its Wordbrew documentation is limited, so if the window asks for something unexpected, look in your Wordbrew account settings before trying again.
03Can Wordbrew start a Make scenario in real time?
No. Wordbrew has no trigger module in Make, scheduled or instant, so it cannot start a scenario by itself. You have two ways around it. The first is to open the scenario with a trigger from another app, such as a form or a CRM, and add Wordbrew modules after it. The second is to begin with a Wordbrew module and let the scenario schedule run it, every 15 minutes by default, or every minute at the fastest on a paid plan.
04What if a Wordbrew module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. That module sends any request the Wordbrew API accepts, using the connection you already set up, so you are not limited to the 8 other modules. You write the request yourself from the Wordbrew API reference. Keep in mind that Make describes its own Wordbrew documentation as incomplete, which means testing each request with Run once matters more here than on a well documented app.
05Should you use Make or n8n for Wordbrew?
It depends on criteria rather than on a winner. On the Make side the facts are clear: 9 modules, including a search and a generic API call, a Free plan to try them, and a documentation Make itself calls limited. For n8n, first check whether a Wordbrew node exists at all, since this page cannot confirm it. Then compare the two on what you actually need to automate, and on which tool the rest of your scenarios already run.
Same platform

Other docs you might need on this stack.

Browse all integrations