skills.rest
TheViziusGroup
TheViziusGroupOFFICIAL
Explore all skills by this author →
WebsiteGitHub

okta-workflows-deployment

Guides versioning and deployment of Okta Workflows between orgs via flopack import and export.

1|Updated Aug 10, 2026
Search Tags:#deployment#import export#ci validation#workflow promotion#okta workflows#identity automation#flopack
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-deployment-theviziusgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okta-workflows-deployment
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/okta-workflows/skills/okta-workflows-deployment
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-deployment-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving Okta Workflows between Preview/sandbox and Production orgs breaks in non-obvious ways: exports strip all connection information and table data, imports fail on broken helper-flow references, and flopack templates fail CI validation when schema rules are violated. This Skill documents those four quirks so deployments succeed on the first attempt. ## Core Features & Use Cases - Export/Import Behavior: Explains that exports remove all connection information and table data, so card connections must be restored and tables are recreated empty from schema only. - Broken Reference Remapping: Covers how missing helper flows block import completion until a replacement flow is specified. - Flopack Schema Validation: Details workflow.flopack and workflow.json rules including the 50-character name limit matching the folder, connector names matching connectors.json, folder regex ^[a-z0-9_]{2,50}$, and the details object matching the flopack exactly. - Folder Constraints: Documents the maximum folder depth of 5 and that duplicating a folder copies table schema but not data. - Use Case: When promoting a set of flows from a sandbox org to Production, use this Skill to anticipate empty tables, restore card connections, remap missing helper flows, and pass CI validation on the flopack template. ## Quick Start Ask the AI to walk you through exporting an Okta Workflows folder from your Preview org and importing it into Production, including restoring connections and fixing broken references.

Frequently Asked Questions about okta-workflows-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move Okta Workflows from Preview to Production?▼

Export the folder as a flopack from the Preview org and import it into Production. Be aware the export strips all connection information and table data, so you must restore every card connection and reload table data manually after import.

Why are my Okta Workflows tables empty after import?▼

Okta Workflows exports remove all table data and keep only the schema. On import, tables are recreated according to the table schema but are initially empty, so data must be transferred separately.

Why does my Okta Workflows import fail with broken references?▼

The import fails when a flow references another flow that was not included in the export, such as a helper flow called to handle a list. You must specify a replacement flow for each missing reference before the import can complete.

What are the workflow.flopack schema validation rules?▼

workflow.flopack and workflow.json must be valid JSON, the name value is limited to 50 characters and must exactly match the enclosing folder, connector names must match connectors.json, and the details object with flowCount, helperFlowsCount, mainFlowsCount, flos, and tags must exactly match the flopack or CI validation fails.

Does duplicating an Okta Workflows folder copy table data?▼

No, duplicating a folder copies the table schema but not the data, which must be transferred manually. References within the folder repoint to the duplicates, external references stay unchanged, and creation dates reset to the duplication date.

What is the maximum folder depth in Okta Workflows?▼

The maximum folder depth is 5 levels. If an import would exceed this limit, the folder is offered as a top-level folder instead.

Related Skills

Explore More Software Engineering Skills→
bhanu91221bhanu91221
2

packaging-2gp

Automate Salesforce 2GP packaging workflows with sfdx configuration and versioning.

Community
Advanced
modelguidemodelguide
106

mg-local-db-restore

Restore local PostgreSQL databases from .dump backups with health checks.

Official
Intermediate
pyronaurpyronaur

asc-workflow

Run repository-local automation workflows defined in workflow.json via the asc CLI.

Community
Advanced
pdparchitectpdparchitect
13

okta-attack

Audit Okta tenants for authentication, MFA, and API misconfigurations.

Community
Advanced