Resources · Make integration

PowerOffice Make integrationAutomate PowerOffice with Make.

Files that belong in PowerOffice can get there on their own. The PowerOffice Make integration gives you 2 action modules, with no trigger. This guide is for teams new to Make: connect the account, build a first scenario, then learn what each module is for.

Try the PowerOffice integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PowerOffice Make integration do?

The PowerOffice Make integration links your PowerOffice account to Make so a scenario, the automation you build in Make as a chain of bricks called modules, can push files into PowerOffice or call its API. It has 2 modules, both actions: nothing in PowerOffice starts a scenario by itself.

Files collected elsewhere, imported for you. A form tool, a mailbox or a cloud drive receives a document, and Import a File sends it into PowerOffice. Nobody downloads and uploads by hand anymore.

Anything the listed module does not cover. Make an API Call reaches any endpoint of the PowerOffice API with the same connection, so a missing module is rarely a dead end, as long as you are comfortable reading API documentation.

A chain that starts somewhere else. Because PowerOffice has no trigger, the first module of the scenario always belongs to another app or runs on a schedule. That is a design choice to make up front, not a flaw to work around later.

What the page cannot promise: the official documentation gives no limits, no prerequisites and no connection steps specific to PowerOffice, so the steps below follow the standard Make flow. If you also look at n8n, the n8n vs Make comparison lays out the criteria. For a structured way in, see the Make training, and for plan details, Make pricing.

Connect

How do you connect PowerOffice to Make?

  1. 01

    Add a PowerOffice module

    In your scenario, click the +, search for PowerOffice and pick a module. Then click Create a connection. A connection is your PowerOffice account linked to Make once, then reused by every PowerOffice module.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps when several people or several PowerOffice accounts share the same Make workspace. Something like the company name keeps things clear later.

  3. 03

    Authorize and save

    Make either opens a PowerOffice page where you approve access, or asks for a key that PowerOffice gives you. Complete that step, then click Save. The module is now ready to use.

First scenario

Your first scenario with PowerOffice

GoalWhen a file shows up in another app, Make imports it into PowerOffice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here it comes from the app where your files land, since PowerOffice has no trigger.

  2. 02

    Set up the starting module

    Search that app, pick the module that picks up new files, and connect the account. Once connected, Make lists the folders or objects it can read, so you choose from a list.

  3. 03

    Add Import a File

    Click the + on the right of the first module, search PowerOffice, choose Import a File and create the connection. Map the file coming from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one file. Check it reached PowerOffice.

  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 if your plan allows, then switch the scenario on.

Modules

What the PowerOffice modules do

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

PowerOffice1

Import a File

Action

In Make“Imports a new file.”

Import a File takes a document handed over by an earlier module and adds it to PowerOffice, which spares you the download and upload round trip.

When to use it
whenever the file starts life in another tool, such as an attachment received by email or a document dropped in a shared drive, and has to end up in PowerOffice.
Watch out
as an action, it runs once per bundle, so ten incoming files mean ten operations on your plan, and the Free plan handles files up to 5 MB.
PowerOffice2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets a scenario send a request of your own to the PowerOffice API, reusing the connection you already created, so you are not stuck when no ready-made module exists.

When to use it
when the job goes beyond importing a file and you know which endpoint of the PowerOffice API does it.
Watch out
you build the request yourself, so keep the PowerOffice API documentation open and test every call with Run once first.
Need help

Need help automating PowerOffice with Make?

A person reads every message.

FAQ

PowerOffice and Make: common questions

01Is the PowerOffice Make integration free?
Yes, on the Make side. PowerOffice is a standard app, so it is available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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) bring the interval down to 1 minute and count usage in credits, meaning operations, each month. Your PowerOffice subscription is a separate matter this page does not cover.
02What is needed to connect PowerOffice to Make?
A PowerOffice account and a Make account. The documentation names no prerequisite and no specific steps, so the standard Make flow applies: add a PowerOffice module, click Create a connection, optionally name it, authorize Make on the PowerOffice page or paste the key PowerOffice provides, then save. That single connection then serves both PowerOffice modules, Import a File and Make an API Call. If several people share one Make workspace, naming the connection after the company avoids picking the wrong account later.
03Does the PowerOffice integration in Make react in real time?
No, because PowerOffice has no trigger in Make, so nothing in PowerOffice starts a scenario. The scenario starts from another app, for example the tool where your files arrive, or from the schedule on its first module. A new scenario runs every 15 minutes by default, the minimum on the Free plan; paid plans go down to 1 minute. If the starting app offers an instant trigger, meaning one it fires through a webhook as soon as something happens, the chain reacts as fast as that app does.
04What if a PowerOffice module is missing in Make?
Use Make an API Call. It reaches any endpoint of the PowerOffice API with the connection you already set up, so a task the listed modules do not cover can still be done from the same scenario. The trade-off is that you write the request yourself, based on the PowerOffice API documentation. The Make documentation gives no limits for this app, so test each call with Run once before switching the scenario on.
05Should PowerOffice be automated with Make or n8n?
It depends on how you like to work. Make gives a visual editor, more than 3,000 standard apps on every plan and a Free plan to start with; PowerOffice is one of those standard apps. On n8n, check first whether a PowerOffice node exists before comparing. The dedicated n8n vs Make comparison on this site lays out the criteria side by side, without declaring a winner, so the choice rests on your team and your other tools.
Same platform

Other docs you might need on this stack.

Browse all integrations