Help and how-to answers

Pilla

You create a workflow template in the web app’s **Workflow templates** area, then open the **canvas** to build it. The help guide says to start from the **New template** button, give it a **name**, **tag**, and **team(s)**, choose the trigger, add your steps, then **Save as draft** or **Publish** when it’s ready. You can read the full guide here: [Canvas overview](https://yourpilla.com/docs/building-workflows#canvas-overview). In short: 1. Open **Workflow templates** on web. 2. Click **New template**. 3. Fill in the required header fields. 4. Set the trigger. 5. Add and connect your steps. 6. Save as a draft, then publish when you’re happy. If you want, I can also help you pick the right template type for what you’re trying to build.

Pilla

A decision connector drops a Pilla decision into the canvas between two steps and splits the workflow into **Yes** and **No** branches. Pilla reads the upstream workflow context, answers the question you write, and sends the run down the matching branch. Each branch starts empty, and you can build out whichever path you need from there. See the guide: [Decision connector](https://yourpilla.com/docs/building-workflows#decision-connector). If you want, I can also explain how it differs from Open and Gated connectors.

Pilla

Pilla has three roles: Staff, Manager, and Admin. In short: Staff can run workflows; Managers can do that plus build templates and manage people/teams for the teams they belong to; Admins can do all of that across the account and also handle billing and bulk imports. A key extra rule is team visibility: Staff and Managers only see data for teams they’re members of, while Admins can see everything by default. You can read the full guide here: [Roles and permissions](https://yourpilla.com/docs/pilla-overview#roles-and-permissions). If you want, I can also summarise what each role can do in a simple table.

Pilla

You can find it in the **Users** or **Teams** screen on web, depending on what you’re importing. According to the help doc, **bulk import is web only and only Admins can open it**. On the **Users** screen, look for **Import** in the top right to bring users in at once; on the **Teams** screen, the same **Import** button opens the team import page. [Importing teams and users in bulk](https://yourpilla.com/docs/pilla-overview#bulk-imports) If you want, I can also point you to the exact steps for importing users or teams.

Pilla

Scheduled triggers fire a workflow template on a calendar. You can set them to run once at a specific date and time, or repeat daily, weekly, monthly, or yearly. The schedule is set on the trigger node in the workflow canvas, and each occurrence creates a new workflow run for your team to complete. [Scheduled triggers](https://yourpilla.com/docs/building-workflows#triggers-scheduled) If you want, I can also explain the difference between **Run just once** and **Run on a schedule**, or walk you through setting one up.

Pilla

No — a workflow template has just one trigger. The docs say a template can be manual, one-time, recurring, or external, and for external triggers specifically, one template can have only one external trigger. [Workflow templates and workflow runs](https://yourpilla.com/docs/running-workflows#workflow-templates-and-runs-overview) / [External triggers](https://yourpilla.com/docs/building-workflows#triggers-external) If you need the same process to start in more than one way, the usual fix is to make separate templates with the same body.

Pilla

There are 9 pending workflows right now.

Pilla

Pilla has three roles: Staff, Manager, and Admin. - **Staff**: the default role. They can run workflows and send messages, but only see data for the teams they belong to. - **Manager**: can do everything Staff can, plus build workflow templates, manage teams and users, and connect integrations for their teams. - **Admin**: can do everything Managers can, plus see everything across the account and manage billing/integrations account-wide. A key extra layer is **team membership**: Staff and Managers only see workflows, users, and chats for their own teams, while Admins can see all teams by default. You can read the full help article here: [Roles and permissions](https://yourpilla.com/docs/pilla-overview#roles-and-permissions). If you want, I can also tell you how to change someone’s role or how team visibility affects what they can see.

Pilla

Open the **Dashboard** in the web app and click the **Workflow templates** card, or use **Workflow templates** from the sidebar. That view is your template library, and clicking any template opens the canvas where you edit it. [Workflow templates and workflow runs](https://yourpilla.com/docs/running-workflows#workflow-templates-and-runs-overview) If you want, I can also point you to the docs for creating a new template or editing an existing one.

Pilla

I couldn’t find any help article showing a direct SAP HANA integration in Pilla. What the docs do say is that Pilla’s integrations are connected from the Integrations page, and that external triggers/actions only support specific services listed in the app. The relevant help article is [First time orientation](https://yourpilla.com/docs/pilla-overview#first-time-orientation). If you want, I can help you figure out the best Pilla workflow setup around SAP HANA data — for example, whether you’re trying to trigger a workflow, pull data into a briefing, or automate a check.

Pilla

Scheduled triggers fire a workflow template on a calendar. You can set them to run just once at a specific date and time, or repeat daily, weekly, monthly, or yearly. The schedule is set on the trigger node in the canvas, then published. [Scheduled triggers](https://yourpilla.com/docs/building-workflows#triggers-scheduled) A recurring trigger also lets you control when it starts, how often it repeats, and when it ends — for example never, after a set number of occurrences, or on a chosen date. Pilla shows a 7-day preview of upcoming runs so you can check the pattern before publishing. [Scheduled triggers](https://yourpilla.com/docs/building-workflows#triggers-scheduled) If you want, I can also point you to the exact steps for setting one up in the canvas.

Pilla

A workflow template has one trigger that decides when it runs. The docs also say a template can have only one external trigger, so if you need the same process to start from different events, you’d build separate templates with the same steps. [Workflow templates and workflow runs](https://yourpilla.com/docs/running-workflows#workflow-templates-and-runs-overview) | [External triggers](https://yourpilla.com/docs/building-workflows#triggers-external) If you want, I can also point you to the trigger setup steps in the canvas.