Articles in this section

Use tool import steps in a flow

Teena Killa
Updated

You can now call reusable tools directly from flows using the Tool import step with full error visibility and retry support, allowing you to reuse shared logic across integrations without rebuilding it in each flow.

Call a tool from a flow

A tool step is now available in the Flow builder. When you add one, the tool runs in flow mode, meaning it behaves like any other step with batch-oriented execution, run console output, and logging.

Tool_in_flow.png
Supported step configuration options:

  • Input filter

  • Mapper

  • preMap and postMap scripts

  • Response mapping

  • postResponseMap script

Send vs preview

Send executes the tool. Preview shows only the data that would be sent to the tool as input. It does not execute the tool or use any mock configured on tool steps.

Reusing tools across flows and APIs

Once a Tool is created, it can be easily reused:

  • Recommended Tools appear when creating new Tool steps with similar name or description

  • You can filter recommendations by source (Marketplace or account) and sort them

  • Select Use step to reuse an existing tool

Connection handling

  • Connections are suggested when reusing a tool

  • If you don't have access to certain connections, you'll be prompted to reconfigure those connections before proceeding.

  • You can still go ahead and override the connections if needed

Errors and retries

Tool steps follow the same error handling behavior as other flow steps, ensuring parity with existing step types for reliable and predictable record-level error recovery.

  • Errors from tools are shown in the flow run console and run history

  • You can see:

    • Tool name

    • Failing sub-step

    • Error message and key details

If a record fails:

  • You can retry from the parent flow, which resumes execution from the exact failing tool sub-step without re-running the entire flow

  • Retries respect tool-specific execution boundaries and error handling configurations

  • Errors auto-resolve when the same trace key is reused on a subsequent run

  • You can also resolve errors directly from the flow, including errors in tool steps and nested tool steps

Error management lets you:

  • Inspect the source record sent to the tool

  • View the record state at the point of failure inside the tool

  • For nested tools (tools that themselves invoke other tools), the error table identifies which sub-step inside the tool failed

Run console and run history

Tool execution is fully visible within the flow across flow runs:

Runconsole_sub_step.png

  • Each tool sub-step appears in the flow run console and run history

  • You can view:

    • Step status

    • Execution duration

    • Step-level and tool-level statisticsErrors (if any), including nested tool errors and retry and resolution states

Tool steps are visually distinguished (for example, via nesting or labels) so you can easily identify them within the flow.

Test run

The test run experience also surfaces Tool import step behavior, including step-level errors within Tool Import steps, nested tool errors, giving you consistent visibility whether you are testing or running a flow in production.