Resources · Zapier integration

Lytho Zapier integrationAutomate Lytho with Zapier.

The Lytho Zapier integration gives you 5 triggers, 4 actions and 3 searches. Every trigger is instant, so approval requests, new projects, proofs and time off reach your other tools as they happen, and that holds on the free plan too.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lytho Zapier integration actually does

It links your Lytho workspace to the other apps your creative team uses. When something happens in Lytho (an asset waits for approval, a project appears, a task or proof is added, someone books time off), Zapier can pass it on. It also works the other way: other tools can create projects, tasks, time off entries and DAM uploads in Lytho.

Approvals nobody misses. On Asset Approval Requested fires as soon as a reviewer is asked to sign off, so a message can land in the chat channel where your reviewers actually look, instead of waiting in a Lytho inbox.

Projects born from intake. A request filed in another tool can become a Lytho project through Create Project, and Create Task can add the first piece of work under it. One action is a two-step Zap; both together make a multi-step Zap, which needs a paid plan.

Absences on the shared calendar. Time Off Entry Created pushes each new absence out of Lytho, so resource planning in other tools stays honest.

What the integration does not do: it has no update or delete action. A Zap can create a project but cannot edit or close it, and there is no way to move a task once it exists. Update Project exists only as a trigger. Searches find campaigns, projects and project templates by name, nothing else. If you are weighing other platforms, see our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event to show up.
Action
What the Zap does after it starts: the step that creates, sends or moves something for you in another app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; 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 occurs.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app, like a Lytho project, so the following steps can reuse what it found.
Connection
Your Lytho account linked to Zapier once, then reused by every step of every Zap that touches Lytho.
Cost

What a Lytho Zap really costs

Lytho is not a premium app, so it runs on the free plan. The bill depends on actions, never on triggers.

  • Triggerfree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appno, works on the free plan

The trigger costs nothing, however many approvals or projects it sees. Each action that succeeds counts as one task, and an action that fails is not counted. The free plan gives 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below governs polling triggers only; all five Lytho triggers are instant, so it does not apply to them.

Connect

Connect Lytho to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A dialog opens with a search box: type Lytho there and pick it from the list.

  2. 02

    Sign in to Lytho

    Click Add connection. A new tab opens on Lytho: sign in with the account the Zaps should act as. You need an account on Lytho itself before any of this works.

  3. 03

    Grant access

    Approve the access Zapier asks for. The connection then appears on the Apps page and every Zap reuses it. Projects and assets you do not own need read or write access on that account.

First Zap

Your first Zap: a starter task on every new project

GoalEach new Lytho project gets a first task automatically, but only for the projects your filter lets through.

  1. 01

    Build the trigger

    Create a Zap, pick Lytho as the app and New Project as the event, then choose your Lytho connection. The trigger is instant, so there is nothing to schedule.

  2. 02

    Test with a real project

    Click test. Zapier brings back the three most recent projects of the connected account; pick one so every later field is mapped on real data, not a blank example.

  3. 03

    Add the filter

    From the plus icon add Filter, then set the field to look at, the rule and the value. Text rules only work on text, so a mismatched rule means the filter never passes.

  4. 04

    Add Create Task

    Add Lytho with Create Task and fill Task Name, the only required field. Map it from the project so each task reads differently, then test the step and check Lytho.

  5. 05

    Publish

    Click Publish to switch the Zap on. A filter makes this a multi-step Zap, so a paid plan is required; on the free plan, drop the filter and keep two steps.

Triggers

Lytho triggers

5 events start a Zap when something happens in Lytho, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

On Asset Approval Requested

Instant trigger

In Zapier“Triggers when a user asks for approval of an asset.”

Starts your Zap when someone asks for approval on an asset in Lytho. It turns the request into a signal other tools can react to, such as a ping to the reviewer or a line in a review tracker.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your reviewers live in a chat tool and keep missing sign-off requests that only show up inside Lytho.
Watch out
it reacts to the request, not to the decision, so approval or rejection needs to be followed inside Lytho.
2

New Project

Instant trigger

In Zapier“Triggers when a new project is created.”

Fires each time a project is created in Lytho, whoever created it. That makes it the natural starting point for setup work you repeat on every project: a first task, a folder elsewhere, a heads-up to the account lead.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every new campaign project should open with the same kickoff task without anyone typing it.
Watch out
if another Zap creates projects with Create Project, those projects set this trigger off too.
3

Update Project

Instant trigger

In Zapier“Triggers when a project is updated.”

Reacts when an existing Lytho project is changed. Use it to keep a copy of the project somewhere else in step with what the team edits in Lytho.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project list kept in a spreadsheet for leadership has to follow the edits made in Lytho.
Watch out
any change counts, so a project edited five times starts five runs; put a filter after it if only some changes matter, knowing a filter makes the Zap multi-step.
4

New Task or Proof

Instant trigger

In Zapier“Triggers when a new task or proof is created.”

Catches every new task and every new proof the moment either is created in Lytho. Both arrive through the same trigger, so the Zap sees them side by side.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
freelancers outside Lytho should hear about new work assigned to them without being given a seat.
Watch out
tasks and proofs share this trigger, so if only one kind should go through, a filter has to separate them.
5

Time Off Entry Created

Instant trigger

In Zapier“Triggers when a new entry for time off is created.”

Starts the Zap whenever a new time off entry is logged in Lytho, be it a vacation, an appointment or a day off. It lets absence data leave Lytho and reach the tools where people plan their week.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
producers book work on a shared calendar and need to see who is away before assigning anything.
Watch out
it only covers new entries, so an absence changed later does not start the Zap again.
Actions

Lytho actions

Lytho gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Upload an Asset

Action

In Zapier“Upload a file to the DAM Asset Manager”

Puts a file coming from another tool straight into Lytho's DAM, where the team searches for assets. It needs a file and a file name, and handles one file per run.

When to use it
final exports saved in a cloud folder should land in the DAM without a manual upload.
Watch out
include the extension in the file name, which Lytho says improves searching in the DAM.
2

Create Project

Action

In Zapier“Creates a new project.”

Opens a new project in Lytho from data another app sent. Only Project Name is required.

When to use it
a brief submitted through an intake form should exist in Lytho without someone retyping it.
Watch out
a Zap triggered by New Project that also creates projects will feed itself.
3

Create Task

Action

In Zapier“Creates a new task.”

Adds a task to Lytho. Task Name is the one required field, so even a sparse source can create work.

When to use it
a bug or edit reported in a client channel should become a task the studio can schedule.
Watch out
this action does not update tasks; each run makes a new one.
4

Create Time Off Entry

Action

In Zapier“Creates a new time off entry.”

Records an absence in Lytho. It asks for three things: a name for the time off, a start date and an end date.

When to use it
leave is approved in an HR tool and Lytho's capacity view should reflect it automatically.
Watch out
dates coming from another tool must map cleanly into both date fields, or the step fails.
Searches

Lytho searches

3 search steps look for data that already exists in Lytho, so a later step can use it.

A search step finds something already in Lytho and passes it to the next steps. In the editor, the three Lytho searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not a clean single match.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap continues with an empty result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Lytho offers no find-or-create variant, so this option does not show on its searches.
  3. If multiple search results are found?
    Three choices when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a Lytho Zap breaks

Zapier publishes no Lytho-specific help article and no Lytho rate limit. What breaks is what breaks on any Zap.

The four cases below are the ones to plan for before you publish. If a Zap already misbehaves, see our Zapier troubleshooting guide.

  • Old projects never show up

    A Zap reacts only to what happens after it is switched on. Projects, tasks and assets created earlier are not picked up; moving them is a separate job.

  • A Zap that triggers itself

    New Project plus Create Project in the same Zap writes where the trigger watches. Each run starts the next one and burns through your tasks.

  • A bulk import goes quiet

    When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • A search finds nothing

    With the default setting, a Lytho search that comes back empty stops the Zap and skips the steps that relied on it.
Need help

Need help automating Lytho with Zapier?

A person reads every message.

FAQ

Lytho Zapier integration: FAQ

01Is the Lytho Zapier integration free?
Yes, as long as the Zap stays at two steps. Lytho is not a premium app, so the free plan can use it, with 100 tasks a month and Zaps made of one trigger and one action. A filter, a search or a second action turns the Zap into a multi-step Zap, and that requires a paid plan. Start with one trigger and one action, such as an alert on each approval request, and the free plan covers it.
02How many Zapier tasks does a Lytho Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that creates a Lytho task from each new project uses one task per project. Add a second action and each run uses two. An action that fails is not counted, and a search step on its own is not an action that writes anything, though it still makes the Zap multi-step. Watching for approvals, projects or time off never costs a task, however busy Lytho gets.
03Is Lytho on Zapier real time?
Yes for all five triggers. Every Lytho trigger is instant: Lytho tells Zapier the moment the approval request, project, update, task or time off entry happens, and the Zap starts straight away whatever the plan. The polling interval grid, which goes from 15 minutes on the free plan down to one on Team and Enterprise, does not apply to any of them. In the editor, a Zap built on one of these triggers shows a lightning bolt.
04What does it take to connect Lytho to Zapier?
A Lytho account, plus read or write access to anything the Zap should touch that you do not own. In Zapier you open the Apps page, click + Add connection, pick Lytho, sign in in the tab that opens and grant access. The connection is then reused by every Zap. If projects or assets belong to colleagues, check your Lytho permissions first, because the Zap can only do what that account is allowed to do.
05Can a Zap edit or close a Lytho project?
No. The integration has four actions and all of them create something: a project, a task, a time off entry or a DAM upload. There is no update, move or delete action. Update Project is a trigger, so it can tell other tools that a project changed in Lytho, but it cannot change the project itself. Any edit has to happen inside Lytho, or the change has to travel the other way, from Lytho to the tool that needs it.
06What if the Lytho action needed is not on Zapier?
Then the Zapier integration cannot do it, and the gap has to be closed elsewhere. The visible menu is fixed at five triggers, four actions and three searches; anything outside that list, such as editing a task or archiving an asset, is not available in the editor. The options are to restructure the flow around what exists, to do that step by hand in Lytho, or to look at another automation platform that connects to Lytho differently.
07Zapier, Make or n8n for Lytho?
It depends on the criterion. On Zapier, Lytho is ready to use with instant triggers and works on the free plan for two-step Zaps, which suits a team that wants alerts and project creation fast. If the flow needs many steps, the multi-step requirement and the per-action task count become the deciding factors. Compare what each platform offers for Lytho, how it bills, and who will maintain the flow, then choose on those grounds rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations