Push To Display

n8n Workflow Examples

Copy-paste recipes for common scenarios. Each example describes the nodes to add and the parameters to set on the PushToDisplay node.

Simple message update

Add a Manual Trigger, then a PushToDisplay node. The simplest possible send:

ParameterValue
AuthenticationAPI Key
Board ID<your-board-id>
MessageSystem operational

The message appears on the board within seconds of the workflow running.

Styled message

Use a Code node with an expression, or set static values directly on the node:

ParameterValue
MessageDeploy completed
Text SizeLarge
Font WeightBold
Text Color#E8FFF6
Text Background Color#0A4A36
Background Color#0F172A

Combine with an n8n expression for dynamic content — e.g. a message built from workflow data:

Deploy of {{ $json.repository }} completed

Multi-panel dashboard

Update different panels from separate steps or branches of your workflow:

Panel 1 — build status

ParameterValue
Target Panel1
MessageBuild: passing
Content SpacingCompact

Panel 2 — test results

ParameterValue
Target Panel2
MessageTests: 128 passed
Content SpacingCompact

Scheduled daily update

Use a Schedule Trigger (e.g. every day at 08:00) connected to the PushToDisplay node, with the message set as a static or expression value.

Webhook-triggered update

Use a Webhook node as the trigger, then map fields from the incoming request to the node:

Node fieldExpression
Message{{ $json.message }}
Background Color{{ $json.background }}

For example, a GitHub webhook payload can drive a deploy-status board, or a form submission can push a notification to a lobby display.

Next

See the HTTP API for the underlying API, or GitHub Action if you need CI/CD integration instead.