Resources · Make integration

Celestory Make integrationAutomate Celestory with Make.

Can Make pick up what happens in Celestory and pass it on to your other tools? The Celestory Make integration offers one module, a trigger called Watch Messages. This page shows how to link your account, build a first scenario around it, and where the documentation stops.

Try the Celestory integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Celestory Make integration do for you?

The Celestory Make integration lets a Make scenario (the automation you build in Make, a chain of modules) start from the messages Celestory hands over. A module is one brick of that chain. Here there is exactly one: Watch Messages, a trigger that collects messages so the next modules can act on them.

Route every message to a shared table. Watch Messages brings each message into Make as a bundle (one item passed from a module to the next). Add a spreadsheet or database module after it and every message lands on its own row, ready for your team to read.

Alert the right person. The same trigger can feed an email or chat module from another app, so a new message reaches someone without anyone opening Celestory to check.

Keep a history outside the tool. Store each message in a CRM or a document tool you already use, and you get a trace you can search later.

What Make does not give you: no action, no search, and no Make an API Call module for Celestory. Make also warns that its documentation for this app is limited, because little public information exists about it. You will discover the exact content of a message by testing, not by reading. The n8n vs Make comparison helps if you are weighing the two tools, and the Make training covers mapping between modules if that step is new to you.

Connect

How do you connect Celestory to Make?

  1. 01

    Add Watch Messages and open the connection

    In a new scenario, click the +, search for Celestory and pick Watch Messages. Then click Create a connection. A connection is your Celestory account linked to Make once, and every later Celestory module reuses it.

  2. 02

    Name the connection if you like

    Make lets you give the connection a name. It is optional, but a clear label such as the workspace or client it belongs to saves confusion later if you ever link a second Celestory account.

  3. 03

    Authorize Make, then save

    Depending on what Celestory asks, either approve Make on the Celestory page that opens or paste the key Celestory gives you. Click Save, and the module can now read your account.

First scenario

Your first scenario with Celestory

GoalWhen a new message shows up in Celestory, Make sends it to the app of your choice.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario, and click the large + to place the first module. That first module decides when the whole scenario starts.

  2. 02

    Place Watch Messages

    Search for Celestory, choose Watch Messages, and select the connection you just made. Fill in whatever the module asks for; Make lists what it can read once the connection works.

  3. 03

    Add where the message goes

    Click the + on the right of Watch Messages and add a module from another app, a sheet or an inbox for instance. Map the message data from the trigger into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. This is the moment to see what a Celestory message actually contains.

  5. 05

    Schedule and switch on

    Open the clock on Watch Messages. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

What starts a Celestory scenario

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

Celestory1Watch Messages

Watch Messages

triggerIn the docs only

Watch Messages gives you a feed of Celestory messages inside Make, so the rest of your scenario can file, forward or store each one. It is the only way into Celestory from Make.

How it fires
Make checks the app on the scenario's schedule. Its name and listing point to a scheduled trigger, so look for the clock badge on the module when you add it.
When to use it
whenever a message arriving in Celestory should reach a person or a table outside it.
Watch out
Make's docs do not describe the message fields, so run the scenario once and read the bundle before mapping anything.
Need help

Need help automating Celestory with Make?

A person reads every message.

FAQ

Questions about the Celestory Make integration

01Is the Celestory Make integration free?
Yes, as far as Make is concerned. Celestory is a standard app, so Watch Messages is available on the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops a run after 5 minutes, and caps files at 5 MB and data transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute. Every module execution counts as one operation on your plan. Your own Celestory subscription is a separate matter.
02What do you need to connect Celestory to Make?
A Celestory account and a Make account. Make's documentation lists no specific prerequisite for this app, so the generic flow applies: add Watch Messages, click Create a connection, optionally name it, then either approve Make on the Celestory page or paste the key Celestory provides, and click Save. The connection is stored once and reused by the module each time the scenario runs. If the authorization step asks for something you do not have, look for it in your Celestory settings.
03Does the Celestory Watch Messages trigger fire instantly?
No. Everything points to a scheduled trigger: Make polls Celestory on the scenario's schedule instead of being called by Celestory through a webhook. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap; paid plans can go down to 1 minute. The type is deduced from the module's name, not confirmed by Make's docs, so confirm it by looking for the clock badge on the module in the editor. A lightning badge would mean an instant trigger instead.
04What if the Celestory module you need is missing in Make?
It depends on what you need. Make offers only Watch Messages for Celestory and no Make an API Call module, so you cannot send data back into Celestory or search it from Make. Make also says its documentation for this app is limited for lack of public information. If you need more than reading messages, check whether Celestory can hand data to another app Make supports, or ask the team through the help form on this page to look at your case before you build around a gap.
05Should you use Make or n8n for Celestory?
It depends on what you already run. On Make, Celestory means one scheduled trigger and nothing to write back, which is enough if your goal is to move messages into other tools. Many apps also have an n8n node, but this page cannot confirm one for Celestory, so check the n8n node list before choosing. Compare what each tool actually offers for Celestory, then pick the one your team already knows, since you will maintain the scenario there.
Same platform

Other docs you might need on this stack.

Browse all integrations