CentrexIT — ST: Rewst Workflow Naming Standards

Publishedv1

Workflow Naming Conventions Documentation

Based on analysis of 295+ workflows in your organization

1. Primary Prefix Pattern

The most common naming convention follows this structure:

[SOURCE - TYPE] Integration/System: Action Description

Source Prefixes

Prefix	Description	Example
`[REWST - ...]`	Standard Rewst crate/template workflows	`[REWST - TASK] M365: Change User Password`
`[ROC]`	ROC (Rewst Operations Center) workflows	`[ROC] PSA-ServiceNow: Update ServiceNow Ticket`
`[CIT-Prod]`	CIT Production workflows	`[CIT-Prod] Microsoft: User Onboarding`
`[CIT]`	CIT workflows (non-production)	`[CIT] PSA - Update Ticket with User Offboard Links`
`[Rewst Master v2]`	Version 2 master template workflows	`[Rewst Master v2] PSA: Update Datto Ticket`
`[Rewst Master v3]`	Version 3 master template workflows	`[Rewst Master v3] On-Prem: Run PowerShell on Org Domain Controller`
`[Karpel]`	Karpel-specific custom workflows	`[Karpel] Create Avanan MSP Access Token`
`[KarpelBot]`	KarpelBot automation workflows	`[KarpelBot] Send Card to Teams`
`[JBW]`	JBW-specific workflows	`[JBW] [Parent] - Send Graph Custom Email`
`[MAAC-Custom]`	MAAC custom workflows	`[MAAC-Custom] On-Prem: List Users By Filter`
`[App Crate]`	App Platform crate workflows	`[App Crate] List User Available Forms`
`[Josh Testing]`	Developer testing workflows	`[Josh Testing] Groups: Add Or Remove Group Membership`
`[DEV - ...]`	Development/testing workflows	`[DEV - OPTION GEN] EXO: List EXO Users`
`[PROD - ...]`	Production-specific workflows	`[PROD - TASK] Datto PSA: Create Ticket`
`[ROC Testing]`	ROC testing workflows	`[ROC Testing] Approval-Wait Webhook`

2. Workflow Type Suffixes

Within the brackets, a TYPE indicator specifies the workflow’s purpose:

Type	Description	Example
`TASK`	Single-purpose task workflow (subworkflow)	`[REWST - TASK] M365: Get User`
`PROCESS`	Multi-step process workflow	`[REWST - PROCESS] PSA: Create Ticket`
`OPT GEN` / `OPTION GEN`	Option generator workflow for forms	`[REWST - OPT GEN] List Organisations`
`PROC`	Abbreviated process workflow	`[REWST - PROC] User: Change Password`
`CRON`	Scheduled/cron-triggered workflow	`[REWST - CRON] Immy: NewHaloClientAlert`

3. Integration/System Naming

After the prefix, workflows typically specify the integration or system:

Integration Pattern	Examples
`M365:`	`[REWST - TASK] M365: Change User Password`
`PSA:`	`[REWST - PROCESS] PSA: Create Ticket`
`PSA-Halo:`	`[REWST - TASK] PSA-Halo: Upsert Contact`
`PSA-CW:` / `PSA-CWM:`	`[REWST - TASK] PSA-CW: List Company Locations`
`PSA-Datto:`	`[Rewst Master v2] PSA-Datto: Get Priorities`
`PSA-Kaseya:` / `PSA-KaseyaBMS:`	`[REWST - TASK] PSA-KaseyaBMS: Upsert Contact`
`PSA-ServiceNow:`	`[ROC] PSA-ServiceNow: Update ServiceNow Ticket`
`PSA-Freshdesk:`	`[REWST - TASK] PSA-Freshdesk: Upsert Contact`
`PSA-AutoTask:`	`[REWST - TASK] PSA-AutoTask: List Company Locations`
`PSA-NinjaOne:`	`[REWST- TASK] PSA-NinjaOne: Update Ticket`
`RMM-Datto:`	`[REWST - TASK] RMM-Datto: List Child Sites`
`RMM-Ninja:`	`[Rewst Master v2] RMM-Ninja: Run Powershell`
`RMM-CW_Control:`	`[Rewst Master v2] RMM-CW_Control: Run Powershell`
`RMM-ImmyBot:`	`[Rewst Master v2] RMM-ImmyBot: Run Powershell`
`RMM-NAble:`	`[ROC] RMM-NAble: Run Powershell`
`On-Prem:`	`[REWST - TASK] On Prem: Manage Groups`
`Graph:`	`[REWST - OPT GEN] Graph: List Mail Enabled Graph Users`
`EXO:`	`[DEV - OPTION GEN] EXO: List EXO Users`
`BYOD:`	`[REWST - TASK] BYOD: Run Query`
`Jumpcloud:`	`[REWST - OPT GEN] Jumpcloud: List Domains`
`GWS:`	`[REWST - OPT GEN] GWS: List Users`
`NinjaOne:`	`[REWST - TASK] NinjaOne: Run Powershell`
`Immy:` / `ImmyBot:`	`Immy: Session Notes in Halo`
`SuperOps:`	`[REWST - OPT GEN] SuperOps - Get Ticket Priorities`

4. Action Verb Patterns

Common action verbs used in workflow names:

Action	Usage
`Create`	Creating new resources
`Update`	Modifying existing resources
`List`	Retrieving multiple items
`Get`	Retrieving single items
`Run`	Executing scripts/commands
`Add`	Adding to collections
`Remove`	Removing from collections
`Upsert`	Create or update
`Document`	Documentation actions
`Send`	Sending communications
`Sync`	Synchronization workflows

5. Informal/Custom Naming Patterns

Some workflows use informal naming without the standard prefix structure:

Pattern	Examples
Project-based	`Sean's Transcript Project`, `Pax8toBill.com`
Descriptive	`Security Scorecard Report - parent`, `QBR Scheduling`
Simple names	`Playground`, `AutomatedAgent`, `adlumin-test`
Polling/Cron	`MAAC Employee Polling`
Generators	`Month and Year Generator`, `forms_output_generator`
Testing	`Test PS On-Prem`, `ProvTest - PSA: List Tickets`

6. Naming Inconsistencies Observed

⚠️ Note: Some inconsistencies exist in your naming conventions

Space variations in prefixes

[REWST - TASK] vs [REWST- TASK] (missing space)
[REWST TASK] (missing hyphen)

Bracket variations

[[Rewst Master v3] (double bracket)
[CIT PSA: (missing closing bracket before colon)

Capitalization inconsistencies

[Rewst Master v2] vs [REWST - TASK]

Leading spaces

[ROC] PSA-ServiceNow: (leading space)
[Rewst Master v2] PSA-Freshdesk: (leading space)

7. Recommended Naming Convention Template

Based on your existing patterns, here’s a recommended standardized format:

[SOURCE - TYPE] Integration: Action Description

Examples

Use Case	Recommended Name
Task workflow	`[REWST - TASK] M365: Create User`
Option generator	`[REWST - OPT GEN] PSA-Halo: List Tickets`
Production process	`[CIT-Prod - PROCESS] Microsoft: User Onboarding`
Custom cron job	`[CUSTOM - CRON] Immy: Daily Sync`

Knowledge Center