> ## Documentation Index
> Fetch the complete documentation index at: https://uselora.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Lora API — Zapier

> Start a Zap when a shortcut is created, updated, or deleted in a Lora workspace, and create or find shortcuts from a Zap. What each step sends and returns, and how to stop a Zap from running twice for the same event.

> [!NOTE]
>
> The Lora integration for Zapier is not available yet. This page describes what it will send and require.

The Lora integration for Zapier has three triggers, one action, and two searches. A trigger starts a Zap when something happens to a shortcut in one workspace.

| Trigger | Starts when |
| - | - |
| `New Shortcut` | A shortcut that everyone in the workspace can see is created, or becomes visible to them. |
| `Updated Shortcut` | A shortcut that everyone in the workspace can see is changed. |
| `Deleted Shortcut` | A shortcut that everyone in the workspace could see is deleted, or becomes hidden from them. |

| Step | Type | What it does |
| - | - | - |
| `Create Shortcut` | Action | Creates a shortcut, or returns the one that already exists. |
| `Find Shortcut` | Search | Finds a shortcut by name, alias, or shortcut ID. |
| `Find or Create Shortcut` | Search | Finds a shortcut by name. Creates it when there is none. |

A Zap can create and find shortcuts. It can't update, delete, or archive them.

## Requirements

* The workspace is on the Basic plan or above. If it drops to Free, triggers stop sending events and nothing is deleted. Upgrading to Basic or above resumes them. The Create and Find steps fail with a message that names the plan.
* You are an owner or admin of the workspace. Members can't connect Zapier, because a trigger sends the workspace's shortcut content to Zapier.
* The workspace has at most 5 Zapier triggers turned on. Turning on a sixth fails with `quota_exceeded`.

Lora sends only shortcuts that everyone in the workspace can see. Private and unlisted shortcuts are never sent, and Zapier never reads or creates a private shortcut.

## Connect Zapier

Zapier connects to Lora with OAuth, so you don't copy an API key.

**1. Add a Lora step to a Zap**

In Zapier, choose Lora as the trigger or action app and connect your Lora account.

**2. Choose the workspace**

One connection is bound to one workspace. If you are an owner or admin on Basic or above in more than one workspace, Lora asks which one. Connect again to use another workspace.

**3. Approve**

Review the consent screen and approve. Zapier can then subscribe to the workspace's shortcut events, create shortcuts, find them, and list the workspace's tag and folder names.

To end a connection, open **Settings > Security and access** in the workspace and revoke the application under **Authorized applications**. Revoking turns off the connection's triggers. Logging out of Lora does not end it.

### Reconnect after an update

A connection made before Create Shortcut existed runs triggers and Find Shortcut. It can't create shortcuts or fill the Tags and Folder lists. Those steps fail with a message that asks you to reconnect Lora. Zapier doesn't ask again when an integration needs more permissions, so reconnect yourself: in Zapier, open **My Apps**, choose Lora, and select **Reconnect**. Approve the consent screen again.

Your triggers keep running through a reconnect. Each Zap's subscription belongs to the same person and workspace, not to one approval. Turn the Zaps off and on only if a trigger has stopped.

### When a connection ends

A connection also ends, with its triggers, when the person who made it is no longer an owner or admin of the workspace: they leave, are removed or suspended, or their role changes to moderator or member. Restoring their access or role does not restore the connection. To bring the triggers back, the person connects Zapier again and turns each Zap off and on. That subscribes the triggers again.

## What a trigger sends

A trigger sends one item per event.

| Field | Description |
| - | - |
| `id`, `event_id` | The ID of the event, starting with `evt_`. Both fields hold the same value. |
| `event_type` | `shortcut.created`, `shortcut.updated`, or `shortcut.deleted`. |
| `reason` | Why the event was sent, or empty. `New Shortcut`: `inserted` or `became_visible`. `Deleted Shortcut`: `removed` or `became_hidden`. `Updated Shortcut` has none. |
| `event_created_at` | When Lora recorded the event. |
| `shortcut_id` | The ID of the shortcut. |
| `slug`, `url` | The shortcut's slug and its Lora link. |
| `destination` | The URL the shortcut points to. |
| `title`, `description` | The shortcut's title and description. |
| `visibility`, `archived`, `passwordProtected`, `expiresAt` | The shortcut's settings. |
| `createdAt`, `updatedAt` | When the shortcut was created and last changed. |
| `folderId`, `additionalFolderIds`, `tagIds`, `aliases` | The shortcut's folders, tags, and aliases. |

`Deleted Shortcut` sends the event fields and `shortcut_id` only.

Event fields are in snake\_case. The shortcut's own fields keep the names they have in the Lora API, which are camelCase.

The event ID and the shortcut ID are different fields. Two changes to the same shortcut are two events with two event IDs, so both start the Zap.

## Create Shortcut

Create Shortcut makes a shortcut in the connected workspace as the person who connected Zapier.

| Field | Required | Description |
| - | - | - |
| `Destination URL` | Yes | The URL the shortcut points to. |
| `Name` | No | The shortcut's name (`slug` in the API), as in `short/handbook`. Leave it empty and Lora derives one from the destination. |
| `Title` | No | The shortcut's title. |
| `Description` | No | The shortcut's description. |
| `Tags` | No | Tags to add, chosen from the workspace's tags. |
| `Folder` | No | The shortcut's folder, chosen from the folders you can use. |
| `Aliases` | No | Other names that open the shortcut. |

Lora numbers a derived name when the plain one is taken by another shortcut: `handbook`, `handbook-2`, `handbook-3`. It never numbers a name you typed. Before it sends the name, the step removes a leading `short/` and lowercases it. If the name still contains characters a name can't have, such as spaces, the step replaces them with hyphens. `Team Handbook` becomes `team-handbook`, and `Über uns` becomes `ueber-uns`.

Every shortcut the step creates is visible to everyone in the workspace. Zapier can't create private shortcuts.

### Repeats

Running the step again with the same input doesn't make a second shortcut. A request is a repeat when a live shortcut shared with the workspace has the same name and the same destination. A live shortcut isn't archived or expired, and the connected person can see it.

For a repeat, Lora returns that shortcut **unchanged**. It doesn't apply the other fields. A new title, tags, folder, aliases, or description in the second run are ignored.

A name that a live shortcut uses for a different destination fails the step. So does a name that an archived or expired shortcut holds. Choose another name, or leave `Name` empty.

### What Create Shortcut returns

| Field | Description |
| - | - |
| `id`, `shortcut_id` | The ID of the shortcut. Both fields hold the same value. |
| `already_existed` | `true` when the shortcut was already there (a repeat). `false` when the step created it. |
| `slug`, `url` | The shortcut's slug and its Lora link. |
| `destination` | The URL the shortcut points to. |
| `title`, `description`, `visibility`, `archived`, `passwordProtected`, `expiresAt`, `createdAt`, `updatedAt`, `folderId`, `additionalFolderIds`, `tagIds`, `aliases` | The same fields a trigger sends. |

In a step's item, `id` is the shortcut's ID. In a trigger's item, `id` is the event's ID and `shortcut_id` is the shortcut's. Map `shortcut_id` when you want one field that means the shortcut in both.

## Find Shortcut

Find Shortcut takes one input, `Name, alias or shortcut ID`. It accepts `handbook`, `short/handbook`, an alias, or a shortcut ID, such as the `shortcut_id` from a Lora trigger. It reads a name the way Create Shortcut does, so `Team Handbook` finds `team-handbook`.

* It finds a name or alias in the workspace's shared shortcuts.
* It never finds a private shortcut, not even by its shortcut ID.
* It finds nothing for an archived or expired shortcut.
* It returns the same fields as Create Shortcut, with `already_existed` set to `true`.

When Find Shortcut finds nothing, it returns no item.

## Find or Create Shortcut

Find or Create Shortcut runs Find Shortcut with the name. If it finds a shortcut, the Zap uses that shortcut as it is, even when its destination differs from the one in the step. If it finds none, it runs Create Shortcut with the same name and the other fields. `already_existed` tells you which one happened.

The name is required here. It can't be empty, because the step uses it to look the shortcut up.

## Limits

A connection can make 60 requests a minute across Create Shortcut, Find Shortcut, and the Tags and Folder lists. Turning a Zap on or off, and the sample and connection checks, have a limit of their own of the same size and don't count against it. When Lora is over the limit, it answers `429` with a `Retry-After` header, and Zapier retries the step later.

## A Zap that starts itself

Creating a workspace shortcut is an event. A `New Shortcut` trigger sends it, so a Zap that starts on `New Shortcut` and runs `Create Shortcut` starts itself again.

* **It stops by itself** when you map the trigger's `slug` and `destination` into the action unchanged. The second run is a repeat. Lora writes nothing, so no event is sent.
* **It stops after at most one extra shortcut** when you leave `Name` empty. If the trigger's shortcut has its own name, the first run derives a new name and creates one more shortcut. The run after that is a repeat.
* **It doesn't stop** when the name changes on every run, for example `{{slug}}-copy`. Each run creates a new shortcut and starts the next run.
* **It never starts** from a private shortcut, because triggers don't send them.

To avoid the loop, map the name unchanged or leave it empty.

## Events can arrive twice

Lora delivers each event at least once. If Lora can't confirm that Zapier received an event, it sends the event again with the same event ID. Zapier does not drop a repeated event from an instant trigger, so the Zap runs twice for that event.

Most Zaps can run twice without harm. If a step must not run twice, for example posting a message or creating a row, add a de-duplication step that checks `event_id`:

**1. Look up the event ID**

Add **Storage by Zapier** with the action **Get Value**. For the key, map the trigger's **Event ID** field (`event_id`), not the text "event\_id".

**2. Stop repeats**

Add a **Filter** that continues only if the value from the previous step does not exist.

**3. Remember the event ID**

Add **Storage by Zapier** with the action **Set Value**. Map the **Event ID** field as the key again and use any text as the value.

**4. Add your steps**

Put the steps that must run once after these three.

Two copies that arrive at the same moment can both pass the filter before either one stores the ID. A repeat sent after a failed delivery arrives later, so this recipe catches it in most cases.

## When Zapier stops answering

Lora sends events only to Zapier hook URLs on `hooks.zapier.com`. Lora has no fixed IP addresses to allow-list.

A `410 Gone` answer from Zapier means the Zap was turned off. Lora deletes that trigger's subscription, sends nothing more to it, and doesn't email anyone.

For other failures, Lora makes up to eight delivery attempts over about 27 hours. If a trigger has no successful delivery for five days and at least five deliveries ran out of retries, Lora disables the trigger and emails the workspace's owners and admins. To bring it back, turn the Zap off and on again in Zapier.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.