Pricing
Apps
Log in
Start trial

Stop

Deliberately end the run as a clean success at this point — no further steps execute.

1 actionPolling

AI-assisted documentation1 min read

This documentation is compiled from our integration source code, internal specs for Stop, its official API documentation and anonymized requests logs we collect from our support team[2].

Open Stop on WEXTL →

The list below is a reference of every Stop node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.

Open any Stop node module below to inspect its input parameters, outputs, and connection requirements.

StopAction

Stop has no settings and no output; the run ends here as a success.

Look for Stop templates in the WEXTL template library.

Browse templates →
  1. Continue[2]In an error-handler branch, swallow the error and resume the workflow on the success path.
  2. Human in the LoopPause the run for a person to review, approve, or reject before the workflow proceeds.
  3. IgnoreIn an error-handler branch, discard the failed item and stop this path without failing the run.
  4. JS CodeRun custom JavaScript in a secure sandbox — transform data, call helpers, and return a result to the next step.
  5. Aggregate ResultsCollapse a fan-out iteration back into a single bundle — collect and combine the results of every branch.
More apps in Built-in category →
  1. WEXTL® Stop Source Code connector implementation.
  2. Our users use cases and automations.
  3. Official API Documentation for Stop.
  4. WEXTL® visual workflow builder data.

Last updated: Jul 18, 2026 19:12

How we write our apps documentation

How we compile these docs — sources, AI's role, and how we verify.