Resources · Make integration

Cloudpress Make integrationAutomate Cloudpress with Make.

Can Make move your Google Docs through Cloudpress without anyone copying and pasting? The Cloudpress Make integration offers 8 modules: 1 scheduled trigger, 6 actions and 1 search. This guide links your account, builds a first scenario and explains each module in plain words.

Try the Cloudpress integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cloudpress Make integration do for you?

The Cloudpress Make integration links your Cloudpress account to Make, a no-code tool where you chain apps together in a scenario (the automation you build). Once linked, Make can export Google Docs, convert them to HTML or Markdown, follow a job request and react to document exports, without a line of code.

A publishing handoff. A writer marks a draft as ready in another app, Make runs Export a Google Doc, then Get a Job Request Status tells the scenario where that export stands before anyone is notified.

Clean markup for a page builder. A product team that pastes content into landing pages can call Convert a Google Doc to HTML and pass the result straight to the next module, instead of fixing formatting by hand.

An alert after each export. Watch Document Export starts a scenario on Cloudpress exports, so a content manager can get a message or a log line for each one.

Know the limits before you start. The official Make documentation for Cloudpress lists its modules without describing them, and it flags its own text as AI-generated content that may contain mistakes, so check any detail that matters with Cloudpress directly. If you are still choosing a platform, our Make review and the n8n vs Make comparison lay out the criteria, and Make training covers the editor from zero.

Connect

How do you connect Cloudpress to Make?

  1. 01

    Copy your Cloudpress API token

    In Cloudpress, click your avatar and name in the bottom left corner, open the Personal tab and copy the API token shown in the personal details section. You need an active Cloudpress account for this.

  2. 02

    Open the connection window in Make

    Add any Cloudpress module to your scenario and click Create a connection. A connection is your Cloudpress account linked to Make once, then reused by every Cloudpress module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when several people share the scenario. Paste the token you copied, or follow the on-screen instructions, and save.

First scenario

Build your first scenario with Cloudpress

GoalWhen a draft is marked ready in another app, Make exports the Google Doc through Cloudpress and checks the status of that job.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module, taken from the app where your team flags drafts as ready.

  2. 02

    Add Export a Google Doc

    Click the + on the right of that module, search Cloudpress, pick Export a Google Doc and click Create a connection with the token from the steps above.

  3. 03

    Map the document

    Fill the module fields Make shows you, and map the document from the first module rather than typing it, so each new draft that passes through gets its own export.

  4. 04

    Follow the job

    Add Get a Job Request Status with the next + and map what the export sent back to point at that job (Run once shows you which value it is). Every item passed along is a bundle: here, one export request.

  5. 05

    Test, then switch it on

    Click Run once and read the bundles each module received. When the output looks right, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Triggers

What can start a Cloudpress scenario?

1 module starts a scenario when something happens in Cloudpress. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cloudpress as soon as it happens.

Cloudpress1Watch Document Export

Watch Document Export

triggerIn the docs only

Watch Document Export gives your scenario a starting point inside Cloudpress: going by its name, it picks up document exports so the following modules can act on each one. The documentation lists it without a description, so run it once and read the first bundle before you build on it.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan.
When to use it
something should follow a Cloudpress export, such as a note to the editor who owns the document.
Watch out
nothing reaches Make between two checks, so do not promise anyone an instant alert.
Modules

What can each Cloudpress module do?

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

Cloudpress1

Convert a Google Doc to HTML

ActionIn the docs only

Turn a Google Doc into HTML that a later module can drop into a page builder or a web form field. The doc gives no field list, so let Make show you what the module asks for once your connection exists.

When to use it
the destination expects markup, for example a landing page or an email template.
Watch out
run it once and inspect the output before mapping it anywhere public.
Cloudpress2

Convert a Google Doc to Markdown

ActionIn the docs only

Need plain text with light formatting instead of markup? This module converts a Google Doc to Markdown, and every module after it can reuse that text as one piece of data.

When to use it
your site or knowledge base stores its pages as Markdown files rather than HTML.
Watch out
choose one format per destination, since converting the same document twice costs two operations (one operation is one run of one module) for a single result.
Cloudpress3

Export From a Connection

ActionIn the docs only

Here the word connection refers to Cloudpress itself: its name points to the connections set up in your Cloudpress account, not to the Make connection that links your account. The documentation adds nothing more.

When to use it
your Cloudpress account already has a connection you want a scenario to export through.
Watch out
open the module after linking your account and check the options Make lists before assuming what it sends.
Cloudpress4

Export a Google Doc

ActionIn the docs only

This is the module that starts an export of one Google Doc through Cloudpress, which makes it the natural core of most scenarios on this page. Map the document from an earlier module so each draft gets its own run.

When to use it
a draft reaches the stage where it should leave Google Docs and move on.
Watch out
test with a copy of a document first, so a half-finished draft never goes out by accident during your trials.
Cloudpress5

Get a Job Request Status

ActionIn the docs only

Where does a Cloudpress job request stand? This action answers that single question, which lets the rest of the scenario react to the answer instead of guessing.

When to use it
right after an export, when the next step, such as telling the author, should wait for the job result.
Watch out
the documentation says nothing about how long a job takes, so a check placed right after the export may still show it in progress.
Cloudpress6

List Collections

SearchIn the docs only

List Collections returns the collections held in your Cloudpress account. As a search, it can return zero, one or several bundles, one per collection found.

When to use it
you need to pick or check a collection inside the scenario before an export.
Watch out
each bundle it returns runs the following modules once, and every run counts as an operation on your plan, so filter the list early.
Cloudpress7

Make an API call

ActionIn the docs only

When the seven other modules fall short, Make an API call reaches any endpoint of the Cloudpress API with the connection you already created, so there is no second login to set up.

When to use it
you need an operation that none of the listed modules covers.
Watch out
you write the request yourself, so keep the Cloudpress API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating Cloudpress with Make?

A person reads every message.

FAQ

Cloudpress and Make: common questions

01Is the Cloudpress Make integration free?
Yes, on the Make side. Cloudpress is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need your own active Cloudpress account, whose pricing is set by Cloudpress, not by Make.
02What do you need to connect Cloudpress to Make?
An active Cloudpress account and its API token. In Cloudpress, click your avatar and name in the bottom left corner, open the Personal tab and copy the token from the personal details section. In Make, add a Cloudpress module, click Create a connection, give it a name if you like, and paste the token. That single connection then serves every Cloudpress module of your scenarios. The connection name is optional, and your Cloudpress subscription is covered on the Cloudpress pricing page, not in Make.
03Does the Cloudpress Make trigger fire instantly?
No. Watch Document Export is a scheduled trigger: Make checks Cloudpress on the schedule of the scenario, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. Paid plans let you go down to 1 minute. An export that happens right after a check waits for the next one. Cloudpress has no instant trigger in Make, where the app would call Make through a webhook as soon as something happens.
04What if a Cloudpress module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Cloudpress API with the connection you already set up, so you can cover what the 8 listed modules do not. Keep in mind that the Make documentation for Cloudpress describes none of its modules and presents itself as AI-generated content that may contain mistakes. When a detail decides your design, confirm it with Cloudpress before you build on it.
05Should you use Make or n8n for Cloudpress?
It depends on which platform your team already runs. This page covers Make, where Cloudpress has 8 modules, including a scheduled trigger and Make an API call for anything else. Before choosing n8n, check whether it offers a Cloudpress node and what it covers, then compare the two on the modules you really need, how you want to connect the account and who will maintain the scenarios day to day.
Same platform

Other docs you might need on this stack.

Browse all integrations