Zapier is a no-code automation platform tool that connects your favorite apps (such as CRM, Google Forms, Google Sheets, Facebook leads and more), so you can pass data and trigger workflows without writing code.
It lets you create “Zaps” — automated workflows — by linking a trigger (e.g., a form submission) to an action (e.g., sending data to your app). You can connect two or more apps to automate repetitive tasks without coding or relying on developers to build the integration. It’s easy enough that anyone can build their own app workflows with just a few clicks. This guide walks you through setting up a Zap that pushes third-party data into displayed screens.
How does it work?
Zapier Triggers Triggers let you get new data from a connected API, break it down into individual fields, and use that data in the next steps of your Zap. They can run every time something new is added to an API endpoint, pushed to Zapier via a Webhook, or filtered to watch for specific items.
NoviSign Actions Actions let you send data to NoviSign’s integrated API. You can save the data into feed collections and use it in an RSS XML widget or as Custom API objects.
Getting Started Before you begin, you’ll need a Zapier account (a free plan is available). Once registered, you can follow the next section to set up your Zaps.
Step-by-Step: Zap Configuration with API Key
Before setting up a Zap, the user must obtain his personal API key:
Hit Insert a dynamicvalue and choose @customapi to use API Integration data
Hit Insert a dynamic value again and choose previously created API Integration
Now you can use the received dynamic properties
Open player settings -> External Interfaces -> Custom API Integration -> Add
Use the same values as in Step 7:
Type link to API URL field
Specify Integration Name and the same Property key you used in the creative
Specify Refresh interval (sec)
Click Save
In Studio, go to Advanced Settings -> Configurations
Create or edit existing configuration
Navigate to External Interfaces -> API Integration
Use the same values as in Step 7
Return to Studio and apply configuration to Screen
Example Scenarios
To help you understand how Zapier can work with NoviSign, here are a few practical examples.
They show how data from external sources can be automatically sent to NoviSign, mapped to the right fields, and displayed on your screens—making it easier to see how the integration works in real-life situations.
Use Case 1: Track Inventory
Channel Name: “store-123”
Message ID: Map from product ID
Quantity: Map from current stock count
Max messages:100
Use Case 2: Publish Upcoming Events
Channel Name: “events”
Message ID: Dynamic or event name
Start/End Date: Map from event info
Data:Event title, location, etc.
TIP: Once you have finished configuring the new Zap, proceed to the next steps and learn how to integrate data into the screen content