Resources · Zapier integration

Openscreen Zapier integrationAutomate Openscreen with Zapier.

The Openscreen Zapier integration gives you 3 triggers, 0 actions and 0 searches. Each trigger watches for a new contact, at the account, asset or project level, and passes it to whatever app you plug in next. Openscreen starts Zaps; it does not receive data.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Openscreen Zapier integration is good for

Openscreen runs QR code programs for supply chains, online stores and customer engagement. Its Zapier integration does one thing: it notices when a new contact shows up in your Openscreen account, on a given asset or inside a given project, and hands that contact to the next app in your Zap so you do not copy it by hand.

Three typical outcomes. A live contact list: every person added to your account goes straight into a spreadsheet your team already reads, through New Contact in Account. A campaign follow-up: contacts collected on one specific project are sent to your email tool, so that project's audience gets its own sequence. A per-product alert: when a contact is attached to one asset, a message goes to the person in charge of that product line.

The three triggers differ only by scope. Account catches everything, Asset and Project narrow it to one item you choose when you set the trigger up. Pick the narrowest one that fits, it saves you a filter.

What Zapier does not do here. There is no action, so a Zap cannot create or update anything in Openscreen; data only flows out. There is no search step, so a Zap cannot look up an existing Openscreen contact either. And all three triggers work by polling, so nothing arrives the second a contact is added: Zapier checks on a timer set by your plan.

To judge Zapier against other tools, see Make vs Zapier or our Zapier review.

Vocabulary

Zapier vocabulary, in plain words

Seven terms you will meet in the editor. After this section, the page uses them without explaining them again.

Zap
The automation you build on 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. With Openscreen, that event is always a new contact appearing somewhere.
Action
What the Zap does once started: the step that writes, sends or moves something for you, in the app you pick.
Task
The unit Zapier bills. Each action your Zap completes successfully counts as one task on your plan.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant one is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Connection
Your Openscreen account linked to Zapier once, then reused by every Openscreen trigger in every Zap you build.
Cost

What an Openscreen Zap really costs

Zapier bills tasks, and an Openscreen trigger never costs one on its own.

  • Free plan100 tasks a month, two-step Zaps
  • Openscreen triggersNever billed
  • Each action that succeeds1 task
  • Premium appNo

Zapier checking Openscreen for new contacts is free, however often it checks. What you pay for is the action that follows: each one that succeeds is a task, and a failed one is not counted. Openscreen is not a premium app, so it works on the free plan: 100 tasks a month, polling every 15 minutes, and two-step Zaps only. Add a filter or a second action and the Zap becomes multi-step, which takes a paid plan.

Connect

Connect Openscreen to Zapier in three steps

  1. 01

    Go to your apps

    In Zapier, open the Apps page of your account. You need an Openscreen account, plus access to any project or asset you do not own but want the Zap to watch.

  2. 02

    Add Openscreen

    Click + Add connection, type Openscreen in the search box of the dialog that opens and select it from the results. Confirm with Add connection to start signing in.

  3. 03

    Sign in and grant access

    A tab opens on Openscreen. Sign in and allow Zapier into the account. The connection then appears in your list, and every Openscreen trigger in every Zap can reuse it.

First Zap

Your first Zap: project contacts into a sheet

GoalEvery new contact added to one Openscreen project becomes a row in a shared spreadsheet.

  1. 01

    Pick the trigger

    Create a Zap, choose Openscreen as the app and New Contact in Project as the event, then select your Openscreen connection.

  2. 02

    Choose the project

    Pick the Project to watch; the field is required. Run the test: Zapier brings back the three most recent contacts of that project, so you map from a real one.

  3. 03

    Add the spreadsheet step

    Add the action that follows, here a new row in your sheet, and map the contact details from the Openscreen step into its columns.

  4. 04

    Test the action

    Run the action once and open the sheet to check what came back. If a column is empty, go back to the mapping before going further.

  5. 05

    Publish

    Publish the Zap to switch it on. Two steps keeps you on the free plan, where Zapier checks the project every 15 minutes.

Triggers

The three Openscreen triggers

3 events start a Zap when something happens in Openscreen. Zapier checks for them at the interval your plan allows.

1

New Contact in Account

Polling trigger

In Zapier“Triggers when a new Contact is added to an Account.”

Picks up every contact added anywhere in your Openscreen account and starts the Zap with it. It is the widest net of the three, with nothing to choose beyond the connection, so every new person reaches the next step whatever asset or project brought them in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you want one master list of everyone your QR programs collect, in your CRM or a shared sheet.
Watch out
because it catches everything, add a filter if only some contacts matter, which makes the Zap multi-step.
2

New Contact in Asset

Polling trigger

In Zapier“Triggers when a new Contact is added to an Asset.”

Watches a single asset you pick and starts the Zap each time a contact is attached to it. Contacts linked to your other assets are ignored, which keeps the Zap focused on one product or one physical item without any extra step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a product manager wants to hear about every new contact tied to the one item they look after.
Watch out
the Asset field is required, so one Zap watches one asset; a second asset means a second Zap.
3

New Contact in Project

Polling trigger

In Zapier“Triggers when a new Contact is added to a Project.”

Follows one Openscreen project and fires whenever a contact joins it. It sits between the two others in scope: narrower than the whole account, wider than one asset, and it fits campaigns that group several items under one project.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a marketing team runs a seasonal QR campaign as a project and wants its contacts in a dedicated email list.
Watch out
the Project field is required, and the connected account must be able to see that project.
When it breaks

When an Openscreen Zap breaks

Zapier ties no help article to Openscreen, so these are the general traps any Zap starting from its triggers can hit.

Most surprises come from how polling works rather than from Openscreen. For a step-by-step check, our Zapier troubleshooting page covers the usual suspects.

  • Existing contacts are skipped

    A Zap only reacts to contacts added after you switch it on. Everyone already in the account, asset or project stays where they are; moving that backlog is a separate job.

  • A loop through your own tools

    If a later step feeds contacts back into the same place the trigger watches, the Zap sets itself off again and again and eats your tasks fast.

  • A bulk import is held back

    After a mass import of contacts, the trigger can return a huge batch at once. Zapier's flood protection may hold it back instead of running them all.

  • No contact is sent twice

    Zapier remembers which contacts it has already seen on a polling trigger, so the same person does not start the Zap a second time.
Need help

Need help automating Openscreen with Zapier?

A person reads every message.

FAQ

Openscreen Zapier integration: frequent questions

01Is the Openscreen Zapier integration free?
Yes. Openscreen is not a premium app, so its triggers work on Zapier's free plan. That plan gives 100 tasks a month and checks for new contacts every 15 minutes, but it only builds two-step Zaps: one Openscreen trigger and one action in another app. Once you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. The Openscreen side of the Zap never uses a task on its own, whichever trigger you choose.
02How many tasks does an Openscreen Zap use?
None for the trigger. Zapier's checks on Openscreen and the arrival of a new contact are free. Tasks come from the actions that follow: each one that succeeds counts once, and a failed one is not counted. A Zap that sends each contact to a spreadsheet costs one task per contact. If it also posts a message to your team, that is two tasks per contact. Plan your monthly volume on the number of contacts you expect rather than on the number of checks.
03Is Openscreen real time on Zapier?
No. All three Openscreen triggers work by polling: Zapier asks Openscreen for new contacts at a fixed interval and keeps only the ones it has not seen. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. A contact added right after a check waits for the next one. If timing matters, a paid plan shortens the gap, and on paid plans you can also run a check by hand from the editor.
04What does it take to connect Openscreen to Zapier?
An Openscreen account, and access to any asset or project you do not own but want to watch. In Zapier, open the Apps page, click + Add connection, search for Openscreen, confirm with Add connection, then sign in on the tab that opens and grant access. The connection is stored once and every Openscreen trigger reuses it. If a project or asset does not appear in the picker later, check the access of the account you connected.
05Why does New Contact in Asset need an asset picked?
Because the Asset field is required: that trigger watches one asset, not all of them. The same goes for New Contact in Project and its Project field. If you want every contact whatever its origin, use New Contact in Account instead, which needs no choice. If you want a handful of assets but not all, the clean route is one Zap per asset, each on the free plan, rather than a single wide Zap with a filter that pushes you onto a paid plan.
06What if the Openscreen operation you need does not exist?
Then the integration does not offer it today. Zapier shows three visible operations for Openscreen, all triggers on new contacts. There is no action to create or update something in Openscreen and no search step. If you need to write back into Openscreen, the Zap cannot do it; the usual answer is to let Openscreen feed your other tools and handle the rest there. Check the Openscreen app page on Zapier before you design anything, since that list is what the editor offers.
07Zapier, Make or n8n for Openscreen?
Decide on criteria, not on a ranking. On Zapier, Openscreen only sends contacts out, through three polling triggers, and a two-step Zap fits the free plan. So ask yourself: do you only need contacts flowing out, or also writing back? How quickly must they arrive, given the plan intervals? How many contacts a month will you move, and how many steps per contact? Answer those, then compare each tool on the same points with your own volume in mind.
Same platform

Other docs you might need on this stack.

Browse all integrations