Resources · Make integration

Officely Make integrationAutomate Officely with Make.

Can Make handle your Officely schedules and chatbot messages for you? The Officely Make integration gives you 6 action modules and no trigger. This guide connects your account, walks you through a first scenario and explains each module in plain words.

Try the Officely integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Officely Make integration do for you?

The Officely Make integration links your Officely account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick of that chain. Officely brings six of them, all actions, so something else has to start the scenario.

Schedules that appear on their own. A new row in a spreadsheet or a submitted form can feed Create Schedule, and the schedule shows up in Officely without anyone retyping it. Pair it with Delete Schedule when a cancellation should clear it again.

A heads-up sent by the chatbot. Chain Get Schedule and Send a Chatbot Message: Make reads the schedule, then posts a message built from its details. Each item that moves between modules is called a bundle, and every module run on a bundle is one operation, the unit Make counts on your plan.

A mode switch driven by events. Change Mode lets an event in another tool change Officely's mode instead of a person doing it by hand.

Know the limits before you start. Make's own documentation for Officely is marked as limited: it lists the modules but gives no fields and no connection steps specific to the app. Make an API Call covers what the listed modules leave out. If you are still choosing a platform, the n8n vs Make comparison and the Make review set out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect Officely to Make?

  1. 01

    Add an Officely module

    In your scenario, click the + and search for Officely, then pick any of its modules. Make asks for a connection, which is your Officely account linked to Make once and reused by every Officely module. Click Create a connection.

  2. 02

    Name the connection

    The name is optional, but a clear one helps when several people or several Officely accounts share the same Make organization. Something like the team or workspace it belongs to is enough to tell them apart later.

  3. 03

    Authorize and save

    Depending on what Officely asks, either approve Make on the Officely page that opens or paste the key Officely gives you. Then click Save. The module can now read what your account exposes and list the choices in its fields.

First scenario

Your first scenario with Officely

GoalWhen a new request lands in another app, Make creates the schedule in Officely and sends a chatbot message about it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle. Since Officely has no trigger, the first module comes from the app where the request starts, such as your form tool.

  2. 02

    Add Create Schedule

    Click the + on the right of that first module, search for Officely and choose Create Schedule. Pick your connection, then map the values coming from the first module into the fields Make displays.

  3. 03

    Add the chatbot message

    Click the + again and choose Send a Chatbot Message. Write the text and drop in data from the earlier modules, so the message says which schedule was just created.

  4. 04

    Test with Run once

    Click Run once, then send a test request in the first app. Open each module's bubble to read the bundles it received and check in Officely that the schedule exists.

  5. 05

    Set the schedule and switch it on

    On the first module, open Scheduling: a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What each Officely module does

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

Officely1

Change Mode

ActionIn the docs only

Switch Officely into another mode from a scenario, so the change follows the event your scenario starts from instead of waiting for someone to do it. The documentation gives only the module's name, not the list of modes.

When to use it
when an event recorded in another tool, like an approved form, should change how Officely behaves.
Watch out
once connected, open the module and read the options Make lists before mapping anything into it.
Officely2

Create Schedule

ActionIn the docs only

Get a new schedule into Officely without typing it yourself: Make builds it from data that arrived earlier in the scenario, one schedule per bundle. You map the values into the fields Make shows once the connection works.

When to use it
when a row added to a spreadsheet or a form reply should turn into a matching schedule.
Watch out
no field list is documented, so run the scenario once and look at the result in Officely before switching it on.
Officely3

Delete Schedule

ActionIn the docs only

Keep Officely tidy by removing a schedule automatically the moment it stops being relevant. It acts on one schedule for each bundle it receives from the module before it.

When to use it
when a cancellation logged somewhere else should also clear the schedule in Officely, so nobody has to remember it.
Watch out
Make cannot undo a deletion, so test with Run once on a schedule you created just for the test.
Officely4

Get Schedule

ActionIn the docs only

Pull the details of one existing schedule out of Officely so the next modules can reuse them in a message, a sheet or another app. Listed as an action, it should read the one schedule you point to rather than search through all of them.

When to use it
right before Send a Chatbot Message, to put the schedule's details into the text.
Watch out
check which value the module asks for to identify the schedule, then read the bundle it returns after Run once.
Officely5

Make an API Call

ActionIn the docs only

Reach any part of the Officely API that the five other modules leave out, using the same connection you already created. It is the way around a missing module.

When to use it
when you need an Officely feature that has no dedicated module in Make.
Watch out
here you work with the API directly, with no fields to guide you, and Make's documentation for this app is limited; ask Officely which requests it accepts before you build one.
Officely6

Send a Chatbot Message

ActionIn the docs only

Have Officely's chatbot deliver a message for you, written from data the scenario already holds, so people are informed without anyone composing the note.

When to use it
at the end of a flow, after Create Schedule or Get Schedule, to announce what just happened.
Watch out
the module sends one message per bundle and each send counts as one operation, so a run that handles many items sends many messages.
Need help

Need help automating Officely with Make?

A person reads every message.

FAQ

Questions about the Officely Make integration

01Is the Officely Make integration free?
Yes. Officely is a standard app in Make, so its modules work from the Free plan. That plan has limits: 2 active scenarios, at least 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 bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle, so a busy scenario uses more of your monthly allowance.
02What is needed to connect Officely to Make?
An Officely account and a Make account. Make's documentation lists no specific prerequisite for Officely and no dedicated connection steps, so the generic flow applies: add an Officely module, click Create a connection, optionally give it a name, then either authorize Make on the page Officely opens or paste the key Officely provides, and click Save. The connection is then reused by all six Officely modules. If Officely does not show you a key, check its settings for integration access before retrying.
03Does the Officely Make integration react in real time?
Not by itself, because Officely has no trigger module in Make: all six modules are actions. A scenario therefore starts from something else. Either use the scenario's schedule, set on the first module, which runs every 15 minutes by default and never more often than that on the Free plan, or start with another app's trigger. If that app offers an instant trigger, it calls Make through a webhook as soon as something happens, and the Officely modules run right after it.
04What if an Officely module is missing in Make?
Use Make an API Call. With it, any endpoint of the Officely API can be called from the scenario with the connection you already have, which covers what Change Mode, Create Schedule, Delete Schedule, Get Schedule and Send a Chatbot Message do not. Keep in mind that Make marks its Officely documentation as limited, with no field descriptions, so check with Officely which requests it accepts before you build one. Test each call with Run once before activating the scenario.
05Make or n8n for Officely: which one fits?
It depends on the tool your team already uses. On the Make side, the facts are simple: 6 action modules, no trigger, a Make an API Call module for everything else, and availability on the Free plan. The same app often has an n8n node too, so check whether one exists for Officely before deciding. Neither choice is ranked here; compare how each handles your scenario, the modules it needs and how the tool counts usage, using the n8n vs Make comparison linked above.
Same platform

Other docs you might need on this stack.

Browse all integrations