cover
  • •
  • #Release

Tapicker v5.17.14 released 🎉👏

Welcome to Tapicker v5.17.14! This update brings new features, improvements, and bug fixes to make your automation experience smoother and more powerful.

  • Added request method and header support for the Download File block
  • Added execution context switching for the Execute Code block
  • Added variable syntax sugar for custom code
  • Added custom naming when cloning recipes
  • Improved overall UI experience
  • Fixed a bug with custom code return values not being destructured

"Download File" Block Supports Request Method and Headers

The Download File block now supports customizing request methods and headers.
This makes it easier to handle scenarios where file downloads require authentication.

download-file

"Execute Code" Block Supports Switching Execution Context

Previously, custom code could only run in the current page. This had advantages—such as direct interaction with the webpage—but also caused issues when strict CSP policies (e.g., on x.com) blocked execution. (While CSP can be disabled, it never felt elegant.)

Now, if your code doesn’t need to interact with the page, you can switch the execution context of the Execute Code block to Sandbox, making execution both safer and faster.

code-context

Variable Syntax Sugar in Custom Code

In Template Syntax, variables are accessed via @args, @vars, @loops, etc.

However, since JavaScript doesn’t allow variables starting with @, custom code required using $args, $vars, $loops instead—often causing confusion.

With this update, we’ve added preprocessing: if you use @args, @vars, or @loops in your custom code, Tapicker will automatically convert them to $args, $vars, and $loops.

This reduces the learning curve and keeps things consistent.

Custom Recipe Name When Cloning

You can now set a new name right when cloning a recipe.
This makes the process faster and reduces mistakes.

clone-recipe

Improved User Experience

We refined UI details for a cleaner look and smoother interactions.

Fixed: Custom Code Return Value Not Destructured

Fixed a bug introduced in v5.17.8 where custom code return values were not properly destructured.

You may also like