slack-recipes

Slack Recipes Skill - Agent Instructions

DEPENDENCY: Load the workato-recipes base skill first if not already loaded. This skill requires the base Workato knowledge for triggers, control flow, datapills, and recipe structure.

CRITICAL: Pre-Generation Checklist

For EXISTING projects:

1. Read existing Slack .recipe.json files to understand local patterns
2. Check for established domain/scope naming conventions

For GREENFIELD projects:

1. Use skill templates - see templates/feedback-collection.json as reference
2. Use descriptive UUIDs - e.g., trigger-001, post-reply-002

ALWAYS:

1. Ask for connection name - exact name of Workbot/Slack connection in Workato
2. Ask for slash command name - verify it's not reserved (see list below)
3. Ask for domain/scope - avoid reserved words like "feedback", "help"
4. Use descriptive UUIDs - never copy random hex UUIDs from existing recipes

CRITICAL: Environment Configuration Required

Before testing Workbot recipes, verify your Slack app is configured for your Workato environment:

1. Go to your Workbot connection in Workato
2. Open the OAuth profile settings
3. Follow the "Configuring your app manually" instructions
4. Update ALL URLs in your Slack app to match the environment-specific URLs shown
5. Ensure the coak_id parameter matches your OAuth profile ID

When switching environments (e.g., trial → production), ALL Slack app URLs must be updated.

Example URLs (trial environment):

Redirect URL: https://app.trial.workato.com/oauth/callback
Events URL: https://app.trial.workato.com/slack_webhooks/event?coak_id=XXX
Actions URL: https://app.trial.workato.com/slack_webhooks/actions?coak_id=XXX
Data Source URL: https://app.trial.workato.com/slack_webhooks/data_source?coak_id=XXX

Required Slack Bot Token Scopes:

• app_mentions:read, channels:read, chat:write, commands
• files:read, files:write, groups.read
• im:history, im:write, mpim:read
• users:read, users:read.email