Resources · Make integration

Lighthouse by Cloudify Make integrationAutomate Lighthouse by Cloudify with Make.

Can Make create and update your Lighthouse records for you? Yes: the Lighthouse by Cloudify Make integration gives you 4 modules, one trigger and three actions. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Lighthouse by Cloudify integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Lighthouse by Cloudify Make integration do?

The Lighthouse by Cloudify Make integration links your Lighthouse account to Make, so records can start an automation or be written by one. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, like a trigger that watches or an action that writes.

Keep other tools in step with Lighthouse. Watch Record picks up records on the scenario's schedule, and every record travels to the next module as a bundle, meaning one item passed along the chain. From there you can send it to a spreadsheet, a chat channel or another app you already use.

Write into Lighthouse from elsewhere. Create a Record adds a new record when something happens in another app, such as a form being submitted. Update a Record changes an existing one, which keeps Lighthouse aligned when the source data moves.

Reach what the list does not show. Make an API Call uses the same connection to call any endpoint of the Lighthouse API, for the cases the three named modules leave out.

Be aware that Make's own documentation for this app is limited: it says there is not enough public information to describe it fully, so field names and limits are not listed. Test with Run once before you rely on a scenario. If you are still choosing a platform, the Make review and the n8n vs Make comparison can help you decide, and Make troubleshooting covers common errors.

Connect

How do you connect Lighthouse by Cloudify to Make?

  1. 01

    Add a Lighthouse module

    In your scenario, click the + and search for Lighthouse by Cloudify. Pick any of its modules, then click Create a connection. A connection is your Lighthouse account linked to Make once, then reused by every module of the app.

  2. 02

    Name the connection

    Give the connection a clear name if you like, such as the workspace or team it belongs to. This step is optional, but it helps when you later link a second account and need to tell them apart in the list.

  3. 03

    Authorize and save

    Either approve access on the Lighthouse page that opens, or paste the key the app gives you, depending on what the window asks for. Then click Save. The connection now shows in the module and you can fill its fields.

First scenario

Your first scenario with Lighthouse by Cloudify

GoalWhen a record shows up in Lighthouse by Cloudify, Make updates it so it carries the information you set.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot is where the trigger goes, the module that starts everything.

  2. 02

    Add Watch Record

    Search for Lighthouse by Cloudify, choose Watch Record and click Create a connection to link your account. Once linked, Make shows the objects it can read.

  3. 03

    Chain Update a Record

    Click the + on the right of the trigger and add Update a Record. Map the record coming from Watch Record into it, so the update lands on the right item, then set the values you want to write.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open them to check that the right record was read and changed as expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval allowed.

Triggers

What can start a Lighthouse by Cloudify scenario?

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

Lighthouse by Cloudify1Watch Record

Watch Record

triggerIn the docs only

Watch Record hands your scenario the Lighthouse records it finds, one bundle per record, so the rest of the chain can act on each one without you copying anything by hand.

How it fires
this is a scheduled trigger, going by its name, since Make's documentation gives no description: Make checks the app on the scenario's schedule, which is every 15 minutes by default, rather than being told the instant something changes.
When to use it
it is the starting point whenever a Lighthouse record should feed another tool, such as a sheet, a message or a follow-up action.
Watch out
the documentation does not explain which records it picks up, so run it once and read the bundles before you switch the scenario on.
Modules

What can Make do in Lighthouse by Cloudify?

Lighthouse by Cloudify gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Lighthouse by Cloudify1

Create a Record

ActionIn the docs only

Create a Record adds a brand new record to Lighthouse by Cloudify from data that arrives in your scenario, so nobody has to retype it.

When to use it
pick it when an event in another app, like a new form entry, should turn into a fresh Lighthouse record rather than change one that exists.
Watch out
each run adds a record, so a test repeated with Run once can leave duplicates to clean up afterwards.
Lighthouse by Cloudify2

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Lighthouse by Cloudify API with the connection you already set up, which covers the jobs the other modules do not.

When to use it
reach for it only when Watch Record, Create a Record and Update a Record cannot do what you need.
Watch out
you write the request yourself, and Make's documentation for this app does not describe the endpoints, so keep the Lighthouse API reference at hand.
Lighthouse by Cloudify3

Update a Record

ActionIn the docs only

Update a Record changes a record that already lives in Lighthouse by Cloudify, so it keeps matching the source of truth in your other tools.

When to use it
choose it over Create a Record when the item exists and only some of its information has moved, for example after Watch Record hands it over.
Watch out
map the record from an earlier module, otherwise Make does not know which one to change, and an overwrite is hard to take back.
Need help

Need help automating Lighthouse by Cloudify with Make?

A person reads every message.

FAQ

Lighthouse by Cloudify and Make: common questions

01Is the Lighthouse by Cloudify Make integration free?
Yes, it is a standard app, so it works on Make's 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. Every module run on one bundle counts as one operation, which is what Make tallies on your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. The Make pricing page on this site goes deeper into the tiers.
02What do you need to connect Lighthouse by Cloudify to Make?
You need a Lighthouse by Cloudify account and a Make account. Make's documentation lists no specific prerequisites for this app and no official connection steps, so the generic flow applies: add a module, click Create a connection, optionally name it, authorize Make on the Lighthouse page or paste the key the app provides, then click Save. The same connection is then reused by all four modules, including Make an API Call.
03Does the Lighthouse by Cloudify trigger run in real time?
No. Watch Record behaves as a scheduled trigger, a type inferred from its name because the documentation gives no description. Make checks Lighthouse on the scenario's schedule instead of being notified the moment a record changes. A new scenario runs every 15 minutes by default, and 15 minutes is the shortest interval on the Free plan. On a paid plan you can go down to 1 minute, which brings the check much closer to the change.
04What if a Lighthouse by Cloudify module is missing in Make?
It depends on what you need, but Make an API Call is the answer in most cases. It calls any endpoint of the Lighthouse by Cloudify API through the connection you already have, so you are not limited to watching, creating and updating records. Keep in mind that Make's documentation for this app is limited and does not describe the API, so you will need the vendor's own reference to build the request and should test it with Run once.
05Should you use Make or n8n for Lighthouse by Cloudify?
It depends on the criteria that matter to your team. On the Make side, this page covers what is confirmed: 4 modules, a scheduled trigger, two record actions and Make an API Call for the rest. The same app often has an n8n node too, so check whether it exists before deciding. Compare the modules each tool offers for your case, the way each one is billed, and which editor your team is more comfortable using.
Same platform

Other docs you might need on this stack.

Browse all integrations