Push To Display

Zapier

The Push To Display Zapier integration lets you send display updates from 7,000+ connected apps. Any time an event happens in your stack — a new form submission, a failed pipeline check, a mention, or a webhook — your boards update instantly across every device linked to them.

The integration is free to connect and exposes a single Send Update action backed by the HTTP API.

Connect your account

  1. Open the Push To Display Zapier app.
  2. Click Connect account and sign in with your Push To Display account.
  3. Authorize the connection — Zapier uses OAuth2 with your Push To Display login.

Send an update

  1. Start a new Zap and choose a Trigger app — for example, a new row in Airtable, a GitHub status check, or a form submission.
  2. Add an Action step and select the Push To Display app.
  3. Pick the Send Update action.
  4. Fill in the fields:
FieldDescription
Board IDThe board to update. Required.
MessageThe text to display on the board. Required.
Target PanelWhich panel to update (1–4). Defaults to panel 1.
Text ColorMessage text color in hex (#RRGGBB).
Text Sizesmall, medium, or large.
Font Weightregular, semibold, or bold.
Full Panel ModeWhen enabled, content fills the entire panel area.
Content SpacingLine spacing: compact, standard, or spacious.
Text Background ColorHighlight color directly behind the text (#RRGGBB).
Background ColorPanel background color (#RRGGBB).
  1. Map any field to data from your trigger step using Zapier's field picker, then test and turn on the Zap.

Example Zaps

  • Airtable → Send Update — when a new row is added, push the record to a board.
  • GitHub → Send Update — when a check run fails, show build status on a status wall.
  • Typeform → Send Update — when a submission arrives, show it on a lobby display.
  • Webhook → Send Update — drive a board from any system that can send a webhook.

Limits

Your free Sandbox tier includes 1 board and 1,000 messages per month. See Rate limits and quotas for details.

Next

  • Prefer n8n? See the n8n node for workflow automation.
  • Under the hood: the HTTP API is the endpoint this integration calls.
  • Working with CI/CD? The GitHub Action pushes deploy status and build results to any display.