workato

Claude Code skill for managing Workato recipes in the PS&I (Post Sales & Integrations) project.

What it does

• Targeted export manifests — package exactly the recipes you specify (no extras, no config records)
• Package export — export manifest → zip ready for PROD import
• Deployment inspection — check pending/recent PROD deployments and their diffs
• Recipe schema changes — add/remove fields from trigger schemas (API platform + callable recipes)
• Recipe lifecycle — stop / update / start recipes via MCP or REST API

Installation

Quickest path: clone this repo, open Claude Code in the repo directory, then run:

/workato-install

The installer skill walks you through the Workato MCP token and helper scripts.

Manual install

If you prefer step-by-step:

1. Workato MCP token: Settings → API → Developer API clients → create token (wrkaeu-...) Add to ~/.claude/settings.json:

   { "mcpServers": { "workato": { "url": "https://app.eu.workato.com/mcp?dev_api_token=<TOKEN>" } } }
   

2. Restart Claude Code.

Prerequisites

• Python 3 (for helper scripts)
• Homebrew recommended (for packages on macOS)

Usage

Invoke via /workato in Claude Code. Examples:

• /workato → "Create an export manifest for recipes 1856715, 1473915, 1515977"
• /workato → "Check what's pending deployment to PROD"
• /workato → "Add a participants array field to recipe 1856715's schema"

Deployment model

DEV (edit recipes) → export manifest → export package (zip)
                                              ↓
                                    PROD import (manual via Workato UI)

PROD deployment is always manual and reviewed by a human. The skill handles DEV-side preparation only.

Key rules

• Only include assets explicitly named — never auto-infer deps
• No config records (connections, env properties, lookup tables) unless explicitly changed
• DEV and PROD have separate recipe IDs — never assume they match
• All recipes already exist in PROD — work is always additive

Scripts reference