Full list

Supported Triggers & Actions

Everything you can automate between Brix and Codeforces.

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.

New Upcoming Contest

New Upcoming Contest

Runs a set time before each new Codeforces contest starts; regular contests by default, or gym or group contests.

Submission Verdict Updated

Submission Verdict Updated

Runs when a submission by the chosen handle gets its final verdict.

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.

List Unsolved Practice Problems

List Unsolved Practice Problems

List Codeforces problems exactly as the API returns them, in data. Enter a handle to list only the problems that user has not solved. Note: custom problemsets such as acmsguru have only the *special tag, so combining them with other tags returns no problems.

Get Problem Details

Get Problem Details

Get one Codeforces problem with its solved count, exactly as the API returns it, by contest ID and problem index, or by problemset name and index. Note: Codeforces has no single-problem endpoint, so the action reads the whole problemset and picks the problem from it.

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 Codeforces free

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

Frequently Asked Questions

How do I connect Brix and Codeforces?

Sign up for a free viaSocket account, then authorize both your Brix and Codeforces 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 Codeforces 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 Codeforces?

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

Can the integration run in both directions?

Yes. You can set up a workflow where Brix triggers actions in Codeforces, and a separate workflow where Codeforces 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 Codeforces. 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 Codeforces integration is built through a visual, point-and-click interface. Code blocks are available if you want them, but they are never required.