Lighthouse By Cloudify Zapier integrationAutomate Lighthouse By Cloudify with Zapier.
The Lighthouse By Cloudify Zapier integration gives you 1 trigger and 3 actions, with no search. The trigger is instant, so your Zap starts as soon as a record is added or changed, and the app already runs on the free Zapier plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lighthouse By Cloudify Zapier integration actually does
Lighthouse By Cloudify is a tool that keeps an eye on business processes, automated or done by hand, and stores what it sees as records. Plugging it into Zapier lets those records start work in your other apps, or lets your other apps write records into Lighthouse, without anyone copying data across.
Three results come out of it most often. An alert outside Lighthouse: New/Updated Record starts a Zap the moment a record appears or changes, and the next step posts it wherever your team actually reads. A record born somewhere else: Create Record turns an event from another app into a Lighthouse record, with its reference and its possible issue filled in. A record kept current: Update Record rewrites an existing record from another app, once you know its key.
Now the limits. There is no search step here, so Zapier cannot look up a record by a value on its own: you need the record key from an earlier step to fetch or update anything. There is no delete action either. And the single trigger fires on new and updated records alike, so if you only care about new ones, you sort that out yourself with a filter.
If you want to compare tools, see our Lighthouse By Cloudify Make integration page and our n8n vs Zapier page.
Zapier words, in plain English
Seven terms come back on this page. Here is what each one means before you open the editor.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
- Connection
- Your Lighthouse account linked to Zapier once, then reused by every step of every Zap that touches the app.
What a Lighthouse Zap really costs
Lighthouse By Cloudify is not a premium app, so it works on the free plan. The bill is counted in tasks, and only completed actions count.
- Free plan100 tasks per month
- Free plan Zap size2 steps: 1 trigger, 1 action
- Premium appNo
- Trigger cost0 tasks
The trigger costs nothing, however many records it watches. Each action that succeeds counts once, so a Zap with two actions uses twice as much. An action that fails is not counted. The catch on the free plan: it allows 100 tasks a month and two-step Zaps only, one trigger plus one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The polling grid below does not apply to this app, since its trigger is instant.
Connect your Lighthouse account in three steps
- 01
Open the Apps page
From your Zapier account, go to Apps, then click + Add connection. A dialog opens with a search box: type Lighthouse By Cloudify and pick it from the list.
- 02
Add the connection
Click Add connection. A new tab opens on Lighthouse: sign in with the account whose records you want the Zap to read or write. You need an account on the app before this step.
- 03
Grant access
Allow Zapier to use the account. If the Zap must touch records you do not own yourself, make sure your account has read or write access to them, or the actions will fail later.
Your first Zap: post a team alert when a record changes
GoalEach time a Lighthouse record is created or updated, check one field and send a message to your team chat only when it matches.
- 01
Create the Zap
Start a new Zap, then pick Lighthouse By Cloudify as the trigger app and
New/Updated Recordas the event. Choose your connection. - 02
Test the trigger
Run the test: Zapier brings back the three most recent records of your account. Pick a real one, so the next steps are mapped on actual data.
- 03
Add a filter
Click the plus icon, add Filter, then fill the three boxes: the field to read, the rule, the value. Use a text rule for text and a number rule for numbers.
- 04
Add the message
Add the action of your team chat, then map the record fields into the message. This Zap now has three steps, so it needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back. When the message in your team chat looks right, click Publish to switch the Zap on.
The Lighthouse By Cloudify trigger
1 event starts a Zap when something happens in Lighthouse By Cloudify, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New/Updated Record
Instant triggerIn Zapier“Triggers when a new record is added or updated.”
Starts your Zap whenever a record shows up in Lighthouse or an existing one changes, and hands its fields to the next steps. It is the only way into the app from Zapier, so every Lighthouse-driven Zap begins here.
Lighthouse By Cloudify actions
Lighthouse By Cloudify gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Record
ActionIn Zapier“Creates a new record.”
Writes a brand new record into Lighthouse from data that arrived in another app, so a process tracked elsewhere gets its entry without manual typing.
Fetch Record
ActionIn Zapier“Fetch Record List.”
Pulls one record back out of Lighthouse, given its key and the entity it belongs to, so later steps can read its fields.
Update Record
ActionIn Zapier“Updates an existing record.”
Rewrites a record that already exists, so Lighthouse keeps the latest state of a process another app knows about first.
When a Lighthouse Zap breaks
Zapier attaches no help article to this app, so the known failure points are the general ones of any Zap, applied to how Lighthouse works.
Four cases cover most of what goes wrong. If one of them looks like yours, our Zapier troubleshooting page is where to go next.
Old records never show up
A Zap only reacts to records created or changed after you publish it. Anything already in Lighthouse stays where it is; moving that backlog is a separate job.The Zap keeps firing itself
Update Record in a Zap that starts on New/Updated Record writes where the trigger watches. Each update fires the Zap again and burns tasks fast.A big batch is held back
After a bulk import or a migration, a sudden wave of records can be held back by Zapier's flood protection instead of running straight through.A required field is empty
Create Record, Fetch Record and Update Record each have required fields. If the mapped value is empty on a real run, that action fails and the Zap stops there.
Need help automating Lighthouse By Cloudify with Zapier?
A person reads every message.
