- Home
- Resources
- Integrations
- OpenAsset
OpenAsset Zapier integrationAutomate OpenAsset with Zapier.
The OpenAsset Zapier integration gives you 4 triggers, 4 actions and 4 searches. New projects, files, albums and employees can start a Zap, and Zapier can create projects and people, upload files or update a project inside OpenAsset.
Verified Trustpilot reviews · AI, automation & growth agency
What the OpenAsset Zapier integration actually does
OpenAsset is a cloud library for the images and documents of architecture, engineering, construction and real estate firms. The integration links it to Zapier, the tool that chains apps together, in both directions: OpenAsset can start an automation, and other apps can write projects, people and files into it.
A project register that fills itself. New Project sends each project created in OpenAsset to a sheet or a planning tool, so the list the office reads is never a week behind.
Projects opened from the sales side. Create Project builds the project in OpenAsset when a deal is won elsewhere, with its name and a unique code, before anyone uploads the first photo. Sales and production then talk about the same project code.
Files that arrive from outside. Upload File drops a document coming from another app straight into the right category, and Find Category hands it the category to use. Nobody downloads and re-uploads by hand.
What Zapier does not do here. It cannot delete anything in OpenAsset, it cannot change an employee once created, and none of the four triggers is instant: each one waits for Zapier's next check. Albums can start a Zap, but no action creates or fills one.
Weighing other tools first? See n8n vs Zapier or Make vs Zapier.
Zapier vocabulary in one minute
Eight words come back on every Zapier screen. Here is what each one means once OpenAsset is plugged in.
- 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 that starts the Zap, such as a new project in OpenAsset. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: it writes, sends or moves something for you, like uploading a file to OpenAsset.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The monthly count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is reported by the app the moment it happens. OpenAsset's are all polling.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already in OpenAsset, a project or a file, so the steps that follow can use what it found.
- Connection
- Your OpenAsset account, linked to Zapier once, then reused by every step that reads from or writes to it.
What it really costs in tasks
OpenAsset is not a premium app, so it works on the free plan. The bill depends on how many actions succeed, not on how often Zapier looks.
- Trigger0 tasks
- Free plan100 tasks a month
- Free plan Zap size2 steps
- Instant triggers0 of 4
The trigger never costs a task, and neither do Zapier's checks for new projects or files, however frequent. Each action that goes through counts once; one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each stopped at two steps: one trigger, one action. A search step, a filter or a second action makes it a multi-step Zap (anything beyond a trigger plus one action), which needs a paid plan. All four OpenAsset triggers are polling, so the interval of your plan below decides how soon a new item is seen.
Connect OpenAsset to Zapier in three steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. You need an OpenAsset account, plus read or write access to the projects and categories you do not own yourself but want the Zap to touch.
- 02
Pick OpenAsset
Type OpenAsset in the search box of the dialog, select it, then click Add connection. A new tab opens on the OpenAsset side for the sign-in, next to your Zapier tab.
- 03
Sign in and grant access
Sign in to OpenAsset in that tab and grant Zapier access to the account. The connection is saved, then reused by every trigger, action and search in your Zaps.
Your first Zap: every new project in a register and a channel
GoalAdd each new OpenAsset project to a shared spreadsheet and announce it in the team channel.
- 01
Set the trigger
Start a new Zap, pick OpenAsset as the app and New Project as the event, then choose the OpenAsset connection you saved in the previous section.
- 02
Test on a real project
Run the test. Zapier brings back the three most recent projects of the account, and you pick one as the sample the next steps will read from.
- 03
Add the register row
Add Google Sheets as the action and map the project's name and code into your columns. Test the step and check the row it wrote in the sheet.
- 04
Add the channel message
Add Slack as a second action and write the announcement from the same project details. The second action makes the Zap multi-step, so it needs a paid plan.
- 05
Publish
Publish the Zap to switch it on. On Free, a new project shows up within 15 minutes; projects created before publishing are never sent.
The 4 OpenAsset triggers
4 events start a Zap when something happens in OpenAsset. Zapier checks for them at the interval your plan allows.
New Album
Polling triggerIn Zapier“Triggers when a new album is created.”
When someone creates an album in OpenAsset, Zapier spots it on its next check and runs the Zap once for that album. It is the only place albums appear in this integration: no action builds or fills one.
New Employee
Polling triggerIn Zapier“Triggers when a new employee is created.”
A new employee record in OpenAsset starts the Zap, which can then carry that person to your HR sheet, your intranet or a welcome message. Each new employee runs the Zap once.
New File
Polling triggerIn Zapier“Triggers when a new file is uploaded.”
Every file uploaded to OpenAsset becomes a fresh item for Zapier. The Zap then runs once per file, which suits alerts, logs and copies to another storage tool.
New Project
Polling triggerIn Zapier“Triggers when a new project is created.”
This one reports each project created in OpenAsset. It is the natural starting point for anything that should exist alongside the project elsewhere: a register row, a folder, an announcement.
The 4 OpenAsset actions
OpenAsset gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Employee
ActionIn Zapier“Creates a new employee.”
Registers a person in OpenAsset from a first name, a last name and a unique employee code, all three required.
Create Project
ActionIn Zapier“Creates a new project.”
Adds a project to OpenAsset with the two things it cannot do without: a name and a code no other project uses.
Update Project Fields
ActionIn Zapier“Updates the fields for a project.”
Changes the fields of a project that already exists. You point it at the project, which is required, and fill in only what should change.
Upload File
ActionIn Zapier“Upload a new file.”
Sends a file from another app into OpenAsset and files it under a category. The file, its filename and the category are required.
The 4 OpenAsset searches
4 search steps look for data that already exists in OpenAsset, so a later step can use it.
A search step finds something that already exists in OpenAsset and hands it to the next steps. In the editor, the searches sit at the bottom of the Action event list, under SEARCH. Some required fields also offer + Add search step, which inserts the search just before and wires its result in for you. Three settings decide what happens when the result is not the one you expected.
Find Category
SearchIn Zapier“Find a category by id or code.”
Looks up a category by its id or its code and passes it on. It exists mostly to feed Upload File, whose category field is required.
Find Employee
SearchFind or createIn Zapier“Find an employee by id or code.”
Finds a person in OpenAsset by id or employee code. The editor also shows Find or Create Employee: it is this same search with the create box ticked, which then asks for the code and the names needed to create the person.
Find File
SearchIn Zapier“Find a file by id or filename.”
Retrieves a file by its id or its filename, so a later step can share or log it. Whether the filename must match exactly is decided by OpenAsset, not Zapier.
Find Project
SearchFind or createIn Zapier“Finds a project by id or code.”
Locates a project by id or project code and hands it to Update Project Fields. Find or Create Project, also listed in the editor, is this search with the create box ticked: it then asks for the name and code a new project needs.
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 there, and the steps that needed it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks
Zapier attaches no help article to OpenAsset, and no rate limit for the app is documented. What goes wrong comes from the required fields and from how Zapier works in general.
Six cases cover most surprises on this integration. If a Zap still misbehaves after that, go to Zapier troubleshooting.
The Zap that sets itself off
New Project followed by Create Project, or New File followed by Upload File, on the same account: each run creates the very item the trigger watches, and the task count drains fast.Existing items never come through
A Zap only reacts to what happens after it is switched on. Projects, files and people already in OpenAsset are not picked up; moving them is a separate job.The same file, twice
Upload File refuses a file that was already uploaded. A Zap that resends the same attachment stops at that step instead of making a copy.A filename without a known extension
The filename must end in an extension OpenAsset supports, such as .jpg or .pdf. A name mapped without its extension blocks the upload.A bulk import held back
When a migration drops a huge batch of files or projects at once, Zapier's flood protection can hold the batch back instead of running the Zap for each item.No duplicates from polling
Zapier remembers what it has already seen on a polling trigger, so the same project does not start the Zap twice, even if it is checked again.
Need help automating OpenAsset with Zapier?
A person reads every message.



