Block reference / Packages

Block package

A package placed as a single block, with its own named inputs and outputs.

In both appsWarpX BrowserWarpX Phone

A package is a saved group of blocks you reuse across automations; you manage them on the Packages page. When a package has Set package as block on, dragging it from the Packages tab of the block list places it as one block, shown with the package's name, instead of pasting its blocks. Its blocks run inside your run, in the same tab and with the same variables and table.

The Block package block's settings, filled in as in the example below.

Settings

Set package as block

In the package's own settings, not on the block. When off, dragging the package in pastes its blocks one by one.

ExampleChecked
Block inputs

Filled in for you: every block in the package that nothing leads into becomes an input, named after its description. Type over a name to keep your own, hide one with the eye, or drag to reorder. Right-click a block's input dot in the editor and choose Set as block input to add one that was not found.

ExampleOpen shop | New tab > input
Block outputs

Filled in the same way: every output dot left unconnected becomes an output, named after its block's description, and every unconnected error fallback goes out through one Fallback output. What you connect to an output runs after that point in the package. Set as block output on an output dot adds one by hand.

Example
Signed in | Click element > output 1
Fallback | Every error fallback

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

The block's outputs are the ones listed in the package's settings. The run leaves by whichever output its blocks reach, or by Fallback when a block inside fails and its error fallback is on. The block itself has no settings panel.

Example: Reuse a login package

  1. Start
  2. Block package
  3. Get text
Where Block package sits in the example workflow.
  1. On the Packages page, open a package named Shop login that holds New tab, Forms and Click element blocks.
  2. In its settings, turn on Set package as block.
  3. The settings now list Block inputs and Block outputs read off the package: New tab as the input, the Click element block's output as an output. Type Start login over the input's name and Signed in over the output's.
  4. Open an automation, switch the block list to Packages and drag Shop login onto the canvas.
  5. Connect Start to Start login, and Signed in to a Get text block that reads the account name.

Good to know

  • The block holds a copy of the package from when you placed it. After you change the package, click the refresh icon on the block to update it; connections to inputs or outputs that no longer exist are removed.
  • A download icon instead of the refresh icon means the package is not in your Packages list, for example in an imported automation. Click it to save the package there.
  • A package cannot contain a Start block, another package block or Execute workflow; the package editor removes them.
  • The run fails with "Input not found" if it enters the block by an input the package no longer has. Update the block and reconnect.
  • Inputs and outputs keep their ids when the package changes, so connections to the block survive an update as long as the connection point is still there.
  • Settings warns when the package has no input, for example when every block has a connection coming in. Right-click the input dot of the block a run should start at and choose Set as block input.
  • A package whose inputs and outputs were picked by hand keeps them. Its settings offer Detect automatically to switch to reading them off the package.

See also

  • Execute workflow — Run another automation from this one and wait for it to finish.
  • Loop data — Run the blocks after it once for each row, number, list item or element.
  • Conditions — Send the run down one of several paths, depending on values, page elements or code.