The Tenderly CLI provides commands to publish and deploy your Web3 Actions. Use tenderly actions publish to upload Actions to the dashboard without activating them, or tenderly actions deploy to both publish and deploy Actions with active triggers.
Commands tenderly actions build Validates configuration and builds your Actions locally without deploying. Use this to test your code and ensure everything compiles correctly.
tenderly actions publish Publishes Actions to the Tenderly dashboard without deploying them. The Actions are uploaded but their triggers remain inactive.
tenderly actions deploy Publishes and deploys Actions with active triggers. Once deployed, Actions will automatically execute when their trigger conditions are met.
What These Commands Do All three commands follow a similar workflow:
Authenticate & Select Project
Verifies authentication and selects the project (or uses --project flag)
Load Configuration
Reads Actions configuration from tenderly.yaml
Validate Runtime
Ensures the runtime version (v1 or v2) is supported
Parse & Validate Triggers
Validates all trigger configurations and checks for errors
Build TypeScript (if applicable)
Compiles TypeScript code using npm run build
Validate Dependencies
Checks package.json dependencies for compatibility
Validate Functions
Ensures all function locators point to existing files
Upload (publish/deploy only)
Packages and uploads source code and dependencies to Tenderly
Activate Triggers (deploy only)
Enables trigger scheduling for deployed Actions
Build Process TypeScript Projects For TypeScript Actions, the build process:
Installs Dependencies : Runs npm install in the sources directoryCompiles TypeScript : Executes npm run build (runs tsc compiler)Validates Output : Checks that compiled .js files exist in the outDir
npm --prefix ./actions install npm --prefix ./actions run build
Your tsconfig.json must specify compilerOptions.outDir. The CLI validates that all functions compile to this directory.
JavaScript Projects JavaScript projects don’t require compilation. The CLI directly validates and packages .js files.
Validation Trigger Validation The CLI validates all trigger configurations before publishing:
Block Trigger
Transaction Trigger
Periodic Trigger
Webhook Trigger
Alert Trigger
trigger : type : block block : network : - 1 # Ethereum Mainnet blocks : 10 # Every 10 blocks
Validation:
network must be a supported network IDblocks must be greater than 0 trigger : type : transaction transaction : status : - success filters : - network : 1 contract : address : "0x1234..."
Validation:
status must be valid (success, failed, or both)filters must have at least one elementAddresses must match regex ^0x[0-9a-f]{40}$
trigger : type : periodic periodic : interval : 1h # OR cron : "0 * * * *"
Validation:
Must have either interval OR cron (not both)
interval must be one of: 5m, 10m, 15m, 30m, 1h, 3h, 6h, 12h, 1dcron must be valid cron syntax trigger : type : webhook webhook : authenticated : true
Validation:
authenticated defaults to true if not specified trigger : type : alert alert : id : "alert-id-here" # OR name : "My Alert Name"
Validation:
Must have either id OR name (not both)
Execution Type Validation The execution_type field must be either parallel or sequential:
execution_type : parallel # ASYNC invocation (default) # OR execution_type : sequential # SYNC invocation
Parallel (ASYNC):
Multiple instances can run simultaneously
Better for high-frequency triggers
No execution order guarantee
Sequential (SYNC):
Only one instance runs at a time
Subsequent triggers queue up
Guaranteed execution order
If execution_type is omitted, it defaults to parallel.
Function Validation The CLI validates that:
Function locator format is correct: filename:functionName
The file exists in the sources directory (with .ts or .js extension)
For TypeScript: compiled .js file exists in outDir
Dependency Validation If package.json exists, the CLI validates:
Required packages are installed
Package versions are compatible with the runtime
No conflicting dependencies
Package Size Limits The CLI enforces a 45 MB limit for packaged Actions:
Logic (source code) : Maximum 45 MBDependencies (node_modules) : Maximum 45 MB
If your package exceeds these limits, consider:
Removing unused dependencies
Using lighter-weight alternatives
Excluding development dependencies from production builds
Incremental Uploads The CLI uses content hashing to avoid re-uploading unchanged files:
Logic hash : Hash of compiled source codeDependencies hash : Hash of node_modules
If hashes match the previously published version, those parts are skipped, making subsequent publishes faster.
Examples Build and Validate Locally Output: Building actions: - example Validating triggers configuration... Validating actions... Build completed.
Publish Without Deploying Output: Building actions: - example Validating triggers configuration... Validating actions... Publishing actions: - example Published actions: - example (actionId = abc123, versionId = v456) https://dashboard.tenderly.co/project/action/abc123
Deploy to Production Output: Building actions: - example Validating triggers configuration... Validating actions... Publishing and deploying actions: - example Published and deployed actions: - example (actionId = abc123, versionId = v456) https://dashboard.tenderly.co/project/action/abc123
Specify Project tenderly actions deploy --project myusername/my-project
Skips project selection prompt and deploys to the specified project.
Dashboard URLs After publishing or deploying, the CLI outputs dashboard URLs for each Action:
https://dashboard.tenderly.co/{project-slug}/action/{action-id}
Visit these URLs to:
View Action execution logs
Monitor trigger events
Edit Action configuration
Pause or resume Actions
Common Errors Missing TypeScript Config Missing typescript config file in your sources!
Solution: Create a tsconfig.json with compilerOptions.outDir set:{ "compilerOptions" : { "outDir" : "./out" } }
Compiled Files Not Found Unable to resolve path for some of the compiled files: out/example.js
Solution: Ensure:
TypeScript compilation succeeds: npm run build
The outDir matches your tsconfig.json
All imported files are in the sources directory
Invalid Execution Type Invalid execution type async for action example. Supported values: {sequential, parallel}
Solution: Use sequential or parallel in your action spec:Invalid Trigger Configuration Found errors when validating triggers example.trigger.block: blocks must be greater than 0, found -1
Solution: Fix the trigger configuration in tenderly.yaml:trigger : type : block block : blocks : 10 # Must be positive
Function Not Found Invalid locator example:myFunction (file actions/example.ts not found).
Solution: Ensure:
The file exists in the sources directory
The function is exported
The locator format is correct: filename:functionName
Global Flags --project string The project slug in which the actions will be published & deployed
Use this flag to skip project selection prompts:
tenderly actions publish --project myusername/my-project tenderly actions deploy --project myusername/my-project
Build vs Publish vs Deploy Command Validates Compiles Uploads Activates Triggers build✓ ✓ ✗ ✗ publish✓ ✓ ✓ ✗ deploy✓ ✓ ✓ ✓
Use cases:
buildpublishdeploy
Version Control with Git The CLI includes Git commit information when publishing Actions:
This helps track which version of your code is deployed. The commit hash is extracted from your Git repository automatically.
Next Steps
Actions Overview Learn about trigger types and execution modes
Initialize Actions Set up a new Actions project
