Skip to main content
Triggr Studio, at app.triggr-app.com, is where you build your own automations: forms, workflows across every tool you connect (including clients’ on-premises networks) and internal apps. Triggr Core is the ready-made Microsoft 365 catalogue; Studio covers everything beyond it. Both share one sign-in, and the same clients and team.

Welcome to Triggr Studio: how it differs from Core, the two ways to use it and where everything is (1:29).

The Studio Dashboard with a sidebar listing Dashboard, Clients, Forms, Workflows, Internal Apps, Approvals, Manual Steps, Integrations, Distributors, On-Prem, Data, Reporting, Decks, Media, Settings, Tools and Compliance, and cards for Pending Approvals, Pending Manual Steps and Execution Stats for the past 7 days.

Studio's Dashboard. The sidebar lists every area; the table below says where each one is documented.

​
Two ways to use Studio

Self-service

Your team builds and maintains its own forms, workflows and apps, using these guides.

Done for you

Our team builds and maintains workflows for you, with ad hoc build credits or a retainer (typically one or two workflows a month).
Most MSPs choose done for you for Studio: our team has built automations for many MSPs and can advise on best practice. Ask your Triggr account manager. Setting up a new organisation? Start with the Go-live checklist.

​
Build

Work through these in order. Each introduction builds a working example in a few minutes.

Forms

Collect requests from your team or clients, with Microsoft or Google sign-in.

Workflows

Run steps across your tools when a form is submitted, on a schedule or from a webhook.

Internal apps

Build pages Triggr hosts that start workflows and show their results.

​
Find your way around

Who sees what depends on their role: Admins build, Approvers follow requests, Members only use apps. See Roles.