📣 New in Fugo: connect your systems to your screens using the one protocol they all already speak — email.
Almost every tool your business runs on can already send an email. Your monitoring stack emails alerts. Your CRM emails when a deal closes. Your ticketing system, your CI pipeline, your order platform, your automation tools like Zapier and Make, even a one-line script on a server — they all speak email. Email Triggers turn that universal capability into a way to drive your screens: if a system can send an email, it can now put content on a Fugo display — with no API to build and no integration to wait for.
Think of email as the connector between your systems and your signage. You create one trigger, Fugo mints a dedicated inbound address for it, and any system you point at that address can trigger content the moment something happens — an incident fires, a milestone is hit, a status changes. Fugo can even reformat the raw system email into a clean, on-brand signage layout automatically.
Email is the integration you already have
Building a custom integration for every system is slow and expensive. Email sidesteps that entirely — it's the lowest-common-denominator interface that virtually every platform supports out of the box:
Monitoring & alerting — Grafana, Datadog, PagerDuty and similar tools email on threshold breaches. Surface incidents on a NOC or ops-room wall the instant they fire.
CRM & sales — pipe "deal won" or "new signup" notifications onto a sales-floor screen to celebrate wins in real time.
Ticketing & support — route queue alerts or SLA breaches to a support-team display.
Automation platforms — Zapier, Make, n8n and workflow tools can send email as a final step, so any event they can catch becomes a screen update.
Your own systems — a cron job, a CI build, or a single line of script can email the address. No SDK, no auth flow.
How it works
Every trigger gets an address. Create an email trigger and Fugo generates a dedicated inbound address (
trig-xxxx@in.fugo.ai). Point your system at it — that's the whole "integration."Route with filters. Optional sender, subject, and body filters let one system drive the right screen — e.g. only emails from your alerting domain, or with
[critical]in the subject, fire the trigger.Reformat with AI. System emails are often noisy. Add a transform prompt — e.g. "Pull the alert name and severity, show as a bold red banner" — and Fugo reshapes each message into signage before it plays. Leave it empty to display the email as received.
Always the latest. Each new matching email replaces the previous one in place, so the screen always reflects the current state of the system feeding it.
No connection step. Unlike OAuth-based integrations, there's nothing to authorize — the address is live the moment you save.
Get started
Go to Triggers in the left-hand navigation, click New Trigger, and choose the Email source. Set your filters, choose how the email should be formatted, assign your screens, and publish — Fugo hands you the inbound address to plug into any system.
👉 Full walkthrough: Email Trigger Setup
Questions or feedback? Reach us through the chat box in the Fugo CMS or at support@fugo.ai.
Don't have a Fugo account yet? Start a 14-day free trial: www.fugo.ai/app