Introduction to internal apps

An internal app is one or more HTML pages, with your own CSS and JavaScript, hosted by Triggr. Use one when a form isn’t enough: your own layout, several pages, or buttons that start workflows.

Build an internal app: a one-page app that sends a message to a workflow, shared with a password and used from its link (1:22).

The Service desk messages app in Design: Settings, SDK, Hide Preview and Saved in the header, a Home page tab with Add Page, Edit Page and Delete Page, the page HTML in the editor and a preview of a Message the service desk page with a text box and a Send button. — The app editor: pages along the top, HTML on the left, a live preview on the right.

Build your first app

A one-page app your team uses to send a message to a workflow. You need an active workflow with a step that uses {{ ctx.params.message }}; copy its ID from the address bar (app.triggr-app.com/workflows/<id>/design).

Create the app

In Internal Apps, click New App, enter a Name and click Create App.

The Create New Internal App dialog with Name Service desk messages, an empty optional Description, and Cancel and Create App buttons.

Write the page

Click Design on the app’s row, click Add Page, name the page and click Create Page. Paste this into the editor, replace WORKFLOW_ID with your workflow’s ID and click Save.

<!doctype html>
<html>
<head>
  <style>body { font-family: sans-serif; padding: 24px; }</style>
</head>
<body>
  <h1>Message the service desk</h1>
  <textarea id="message" rows="4" cols="40"></textarea>
  <p><button id="send">Send</button></p>
  <p id="status"></p>
  <script>
    document.getElementById('send').addEventListener('click', async () => {
      const status = document.getElementById('status');
      try {
        const { executionId } = await triggr.runWorkflow('WORKFLOW_ID', {
          message: document.getElementById('message').value
        });
        status.textContent = 'Sent (run ' + executionId + ')';
      } catch (err) {
        status.textContent = err.message;
      }
    });
  </script>
</body>
</html>

Secure it

Click Settings, choose Password as the Authentication Type and enter a password. Under Workflows pages can run, tick your workflow, then click Save Settings.

The App Authentication panel with Password selected, Hide top bar and List on Homepage off, a masked Password, Allow file uploads off, and Service desk message ticked under Workflows pages can run.

Test and share it

Back on Internal Apps, click Share on the app’s row, then Open in new tab. Enter the password and send a message: the run appears under Executions. Click Copy and send your team the link and password.

The Share App dialog with a Public App URL on forms.yourmsp.com, a Copy button and an Open in new tab link.

Who can open an app

New apps start as Internal: your Studio team opens them at https://app.triggr-app.com/telescope/apps/<org-id>/<app-id> with their staff sign-in (Support > Copy Org ID in the top bar gives the first ID; the second is in the designer’s address bar). None, Password, Microsoft and Google work as they do for forms and add a Share link. A Microsoft or Google visitor’s workflows run for their client. Allow file uploads needs Microsoft, Google or Internal authentication. Hide top bar shows only the first page, full-screen.

The Triggr SDK

In the live app (the Share link, or the Internal app URL above), each page gets window.triggr, which acts as the signed-in visitor: runWorkflow starts a ticked workflow and returns its executionId, and upload, pickAndUpload, list and fileUrl handle files when Allow file uploads is on. Preview and Open show a page’s layout, not its calls, so test calls in the live app. Click SDK in the editor for the quick reference.

SDK reference: every call, its limits and errors, and when to use a workflow’s webhook instead.
Example: build an uptime monitor: workflows on a schedule, results in a database, and a page that shows them.

Troubleshooting

this app is not allowed to run that workflow

Tick the workflow under Settings > Workflows pages can run and click Save Settings, and check the ID in the page matches the workflow’s.

workflow is not active

On Workflows, click Edit on the workflow’s row, set Status to Active and click Save Changes.

“triggr is not defined” or “Triggr is not available on this page”

The page was opened with Open, which shows it without the SDK. Use Share > Open in new tab, or the Internal app URL above.

New App is missing

Ask an admin for permission to edit internal apps.

Next: Example: build an uptime monitor.

Get started

Clients and access

Forms

Workflows

Internal apps

Automation

On-prem

Data and files

Reporting

Settings

AI tools

Build your first app

Who can open an app

The Triggr SDK

Troubleshooting

​Build your first app

​Who can open an app

​The Triggr SDK

​Troubleshooting

Build your first app

Who can open an app

The Triggr SDK

Troubleshooting