Script Actions

Script Actions run custom JavaScript against workflow and record context. Use them for logic that cannot be expressed clearly with standard actions.

Define the input record, allowed Types, limits, and expected outputs before writing code. Keep scripts focused, validate incoming values, and log enough information to diagnose a failed run.

Scripts can return summaries, record IDs, files, logs, and custom outputs for later actions. Treat them as production code: review changes, test edge cases, and control the records they may update.

Prefer standard actions when they meet the requirement; they are easier for future builders to understand and maintain.