Toolkit

Custom Endpoints

Custom Endpoints let workflows call saved HTTP request templates so browser automation can hand data to your own APIs and services.

IntegrationsAPI

What It Does

Custom Endpoints bridge browser automation and external systems. Instead of rebuilding the same request in every workflow, you save it once and call it through the workflow editor.

How It Works

  • A saved endpoint stores the URL, method, headers, body, response path, and output variable.
  • The workflow Call Endpoint step looks up the saved endpoint by id.
  • Variables are interpolated into the URL, headers, body, and response path before the request is made.
  • The selected response can be saved back into workflow variables for later steps.

Best For

  • Sending page content to your own API
  • Calling Python or Node backends
  • Resume rewrite and content generation services
  • Mixing browser automation with external systems

Behavior Notes

  • Headers JSON and Body JSON should be valid JSON objects.
  • Response path lets you save only the nested value you need instead of the full response.
  • The built-in endpoint editor also supports request testing and cURL import.