push-project

/push-project

Push local changes to the Workato remote and verify the recipes work.

Usage

• /push-project — push the current project
• /push-project <project-name> — switch to the specified project and push
• /push-project --start — start the recipes after pushing
• /push-project --test — start the recipes and verify job success after pushing
• /push-project --restart-recipes — auto-restart any running recipes after push (for updates)
• /push-project --delete — delete assets that exist remotely but not locally
• /push-project --validate-only — only validate (do not push)

Procedure

0. Environment guard (mandatory)

Before any validation or push, confirm the push target is dev. See @.claude/rules/workato-deployment-flow.md for the full rule.

python3 scripts/workato-api.py profile show

• Hard-block: if the resolved profile name does not end with -dev, abort immediately. This covers -test, -prod, -production, -staging, -qa, and any other non-dev suffix. Do not offer a confirmation prompt — the rule is inviolable.
• The only way to proceed is for the user to either (a) switch to a -dev profile, or (b) rename their dev profile to follow the <org>-dev convention. Tell the user which option applies.
• Direct push to test/prod is forbidden; promotion goes through the Deploy feature (@docs/platform/environments.md).

1. Project validation

Validate the project's JSON files before pushing. With --validate-only, stop here.

1a. JSON syntax check

Check the syntax of every JSON file under the project directory:

# Targets: *.recipe.json, *.connection.json, *.agentic_genie.json,
#          *.agentic_skill.json, *.mcp_server.json, *.lcap_app.json,
#          *.lcap_page.json, *.workato_db_table.json
for f in projects/<project-name>/*.json; do
  python3 -c "import json; json.load(open('$f'))" 2>&1 || echo "INVALID: $f"
done

Fix any errors before continuing.

1b. extended_output_schema check