Lyra Zapier integrationAutomate Lyra with Zapier.
The Lyra Zapier integration offers 3 triggers, 2 actions and 1 search. The triggers are all instant, so a new board, a status change or a new stakeholder can start a Zap at once, and the actions let other tools invite people or move a board along.
Verified Trustpilot reviews · AI, automation & growth agency
Why connect Lyra to Zapier
Lyra is an AI whiteboard built for sales teams: each Lyra is a shared canvas where you talk a deal through, work on it together and push it to a close. Zapier connects it to your other tools through a Zap, an automation that starts on one event and then runs one or more steps every time that event happens, in both directions here.
With three triggers, two actions and a search, the traffic goes both ways. Three results come up most often.
Every stakeholder in your CRM. New Stakeholder sends each person captured on a Lyra to your CRM as a contact, so the people around a deal stop living only on the canvas. A status change everyone hears about. New Lyra in Status posts in your team chat when a board moves to a new status, which keeps managers informed without opening Lyra. Invites sent from a form. When someone fills in your form, Find Lyra locates the right board and Create Stakeholder invites them to it by email.
What the integration does not do: it reports nothing that happens inside the canvas beyond the three events listed below, so any other change on a board never starts a Zap. And both actions work on a Lyra that already exists, so the Zap has to know which one.
Weighing builders before you start? See our Make vs Zapier comparison and our Zapier review.
The Zapier words you need, in one minute
Eight terms come back throughout this page. Each one is explained here once, in everyday English.
- Trigger
- The event in an app that starts a Zap. Once the Zap is on, Zapier waits for that event and does nothing before it.
- Action
- What the Zap does once it has started: the step that writes, sends or changes something for you in an app.
- Task
- The unit Zapier bills: one action completed successfully. The allowance on your plan is counted in tasks.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items and keeping only what it has not seen before.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. All three Lyra triggers work like this.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists, such as a Lyra, so the steps after it can use what it found.
- Connection
- Your Lyra account, linked to Zapier once and then reused by every trigger, action and search step that uses Lyra.
What it really costs
The three Lyra triggers are free: waiting for an event never costs a task. What counts is each action your Zap completes, in Lyra or anywhere else.
- TriggersFree, never counted as tasks
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- Search stepMakes the Zap multi-step, so a paid plan
Every action that succeeds is counted on its own, so a three-action Zap uses three times what a one-action Zap uses, and an action that fails is not counted. Lyra is not a premium app, so it runs on the free plan, which builds Zaps of two steps: a trigger and one action. A filter, a search such as Find Lyra, or a second action turns it into a multi-step Zap, which needs a paid plan. The interval grid below sets how often polling triggers are checked; it does not apply to the Lyra triggers, which are all instant.
Connect Lyra to Zapier in 3 steps
- 01
Open Apps
In your Zapier account, open Apps and click + Add connection. Type Lyra in the search box of the dialog and pick it from the list. You need a Lyra account first.
- 02
Sign in to Lyra
Click Add connection. A tab opens on Lyra: sign in with the account that holds your boards. If some Lyras belong to a colleague, check that your account can read them and, for the actions, write to them.
- 03
Grant access
Approve the access Zapier asks for. The tab closes and the connection shows up in your Apps list, ready for every trigger, action and search that uses Lyra.
Your first Zap: send new stakeholders to your CRM, selectively
GoalWhen a stakeholder is captured on a Lyra, keep only the ones that match your condition and create them as contacts in your CRM.
- 01
Create the Zap and pick the trigger
Start a new Zap, search Lyra and choose
New Stakeholder, then the connection you made earlier. A lightning bolt appears in the editor: the trigger is instant. - 02
Test on a real stakeholder
Run the test. Zapier brings back the three most recent items of your account, so you can see which field tells the people you want apart from the rest.
- 03
Add the filter
From the plus icon, add the Filter step and fill its three boxes: the field to look at, the rule, the value to compare with. The filter makes the Zap multi-step, so it needs a paid plan.
- 04
Create the contact
Add your CRM as the action with its create-contact event, then drop each stakeholder detail from the test into the matching contact field so nothing is retyped later.
- 05
Test and publish
Run each step once and check the contact that landed in your CRM. When it looks right, click Publish to switch the Zap on for every new stakeholder.
The three Lyra triggers
3 events start a Zap when something happens in Lyra, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
New Lyra in Status
Instant triggerIn Zapier“Triggers when a Lyra enters a new status.”
Starts your Zap each time a Lyra moves into a new status. It is the trigger that follows a deal board through its stages, so the rest of your tools can react when the board changes state.
New Lyra
Instant triggerIn Zapier“Triggers when a new Lyra is created.”
Fires when someone creates a Lyra. Each new board becomes a starting point for whatever has to happen around a fresh deal in your other tools.
New Stakeholder
Instant triggerIn Zapier“Triggers when a new stakeholder is captured.”
Reacts when a new stakeholder is captured on a Lyra. That person can then reach your CRM, your email list or your team without anyone copying their details by hand.
The two Lyra actions
Lyra gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Update Lyra Status
ActionIn Zapier“Update status of an existing Lyra.”
Moves an existing Lyra to another status from outside the app. The board follows what happens in your other tools instead of waiting for someone to update it.
Create Stakeholder
ActionIn Zapier“Invite stakeholders to an existing Lyra.”
Invites people to a Lyra that already exists, by email. Your Zap names the board and passes one or more addresses, and they are added to it as stakeholders.
The Lyra search
1 search step looks for data that already exists in Lyra, so a later step can use it.
A search step finds a Lyra that already exists, so the actions after it know which board to work on. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not exactly one board.
Find Lyra
SearchFind or createIn Zapier“Finds a Lyra in the organization.”
Looks up a Lyra in your organization and hands it to the next step, which is how Create Stakeholder or Update Lyra Status gets the board it needs. The editor also shows Find or Create Lyra: it is this same search with the create box ticked, not a separate operation.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that needed it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?X stands for the item searched. Ticking it turns the search into a find-or-create: the setting above disappears and Zapier asks for the fields needed to create the missing board.
- If multiple search results are found?Three ways out when several boards match: keep the first one, which is the default, stop the Zap, or hand all of them to the next steps.
When it breaks
Zapier links no help article to Lyra and records no limit specific to the app. What goes wrong comes from Zapier's general behaviour and from how the Lyra operations fit together.
Read these cases before you publish: none of them shows up as an obvious error. If a Zap still misbehaves, see our Zapier troubleshooting page.
A status Zap that feeds itself
A Zap started by New Lyra in Status that runs Update Lyra Status writes where its own trigger watches. It sets itself off again and burns through tasks.Boards from before are ignored
A Zap only reacts to what happens after it is switched on. Lyras and stakeholders that already existed are never picked up; moving them is a separate job.A bulk change is held back
If a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the run back rather than fire for each item.The search finds nothing
With the default setting, a Find Lyra that comes back empty stops the Zap there, and Create Stakeholder or Update Lyra Status never runs.The search step will not publish
Find Lyra, a filter or a second action make the Zap multi-step. On the free plan, only a trigger followed by a single action can go live.A filter that blocks everything
Filter rules are typed: a text rule only works on text, a number rule only on numbers. The wrong type is why a filter on a status never passes.
Need help automating Lyra with Zapier?
A person reads every message.
