Integrations Brix viaSocket utilities
Brix + viaSocket utilities
Full list

Supported Triggers & Actions

Everything you can automate between Brix and viaSocket utilities.

When this happensTriggers

A trigger is an event that starts a workflow.

New Recalled Content

New Recalled Content

Runs when a file, design, playlist or schedule is recalled from all screens.

New Restored Content

New Restored Content

Runs when recalled content is restored to screens.

New Screen

New Screen

Runs when a new screen is added, optionally within a chosen location.

New Media

New Media

Runs when a new file is added to the media library, optionally of chosen types.

Request a new Trigger for Brix

Do thisActions

Action is the task that follows automatically within your Brix integrations.

Import Media from URL

Import Media from URL

Add an image, video or file to the media library from a public URL.

Create Playlist

Create Playlist

Create a new playlist with optional dates, shuffle and location.

Add Item to Playlist

Add Item to Playlist

Append media, a playlist, app, layout or ad slot to a playlist.

List Screens

List Screens

List screens, search them by name, or get one screen by ID.

Pause Workflow

Pause Workflow

Pause workflow for X minutes

Flow in Flow

Flow in Flow

Run another workflow from your current workflow. API inputData (Apps API key Flow_in_Flow, auth NoAuth): - flowid (required): child flow script id in the same project. - methodOfPayload (required): "keyvalue" or "bulk" (default keyvalue). - inputbody: object when methodOfPayload is keyvalue (child webhook body fields). - bulkpayload: JSON string or object when methodOfPayload is bulk (child webhook body). Full field labels and sample: https://viasocket.com/docs/viasocket-utilities/flow-in-flow.md This action can be configured with: Flow To Run (The child flow's script id (same project as this flow). In the UI, pick from the list; in API calls, set flowid to that id.) Payload (When methodOfPayload is "keyvalue": nested fields matching the child flow webhook body (generated after you pick the flow).) Payload (When methodOfPayload is "bulk": a JSON string (use JSON.stringify) or object for the child flow webhook body—the same shape as context.req.body on the child flow. Required in bulk mode.) Method to fill Payload (How to send data to the child flow: "keyvalue" (Key-Value Pair) maps fields one by one; "bulk" (Bulk Insert) sends one JSON payload.): enum: ["Key-Value Pair", "Bulk Insert"]

How to build your first workflow with viaSocket
2-Minute Guide

Learn how to build your first workflow

Follow a simple walkthrough to create, test, and launch your first automation.

  1. 1

    Connect your apps

    Link the apps you want to automate.

  2. 2

    Configure your workflow

    Set up triggers, actions, and map your data.

  3. 3

    Test & publish

    Test your workflow and publish it.

Trusted by Thousands. Recognized by the Best.

Recognized by leading review platforms and trusted by 10,000+ businesses worldwide.

Workflow: Auto Close Inactive viaSocket Connections
YOU
◆AI Workflow Builder

From idea to automation.
AI will build it for you

Just describe the task in plain English. viaSocket AI selects the right apps, builds the workflow, maps the fields, and prepares everything for review before you publish.

No coding required|Review before publishing|Works with 2,300+ apps
Create with AI

Need help building your workflow?

Get help instantly from AI or reach out to our support team.

viaSocket Support

We're here to help

Online
Support agent
What can I help you with?
How can I set trigger?
10:30 AM ✓

Instant answers

AI assistant available 24/7

Expert support

Connect with our specialists

Trusted & secure

Your data is safe with us

Start automating Brix and viaSocket utilities free

No credit card required. Set up your first workflow in minutes.

Integrations viaSocket utilities
viaSocket utilities + Brix
viaSocket utilities logo

About viaSocket utilities

Utility services for viasocket.com provide essential tools and functionalities to enhance and streamline workflow automation, enabling users to connect various applications and automate tasks efficiently.

Learn more

Frequently Asked Questions

How do I connect Brix and viaSocket utilities?

Sign up for a free viaSocket account, then authorize both your Brix and viaSocket utilities accounts. From there, pick a trigger in one app and an action in the other. Your first workflow can be live in under five minutes.

Does this integration work in real time?

Yes. viaSocket uses instant triggers where available, so data moves between Brix and viaSocket utilities as soon as the event happens. Scheduled polling triggers run at a maximum interval of 15 minutes.

Can I control which data gets sent from Brix to viaSocket utilities?

Yes. You can map specific fields, apply filters to skip records that do not match your conditions, and transform values before they reach viaSocket utilities. No coding required.

Can the integration run in both directions?

Yes. You can set up a workflow where Brix triggers actions in viaSocket utilities, and a separate workflow where viaSocket utilities triggers actions in Brix. Both run independently and in real time.

What happens if a step in the workflow fails?

viaSocket logs every run so you can see exactly what succeeded and what failed. Failed tasks can be retried from the dashboard without re-configuring the workflow.

Is viaSocket free to use?

Yes, there is a free plan that covers basic workflows between Brix and viaSocket utilities. Paid plans unlock higher task limits, faster polling, and advanced features like multi-step workflows and conditional logic.

Do I need to know how to code to set this up?

No. The entire Brix and viaSocket utilities integration is built through a visual, point-and-click interface. Code blocks are available if you want them, but they are never required.