Toolkit

Custom Endpoints

Create reusable HTTP request templates, call them from workflows with the Call Endpoint step, and store selected response values back into workflow variables.

What It Does

Custom Endpoints let you save reusable API request definitions in the plugin and call them from any workflow. They are ideal when browser automation needs to hand off data to a Python service, Node backend, internal API, or content-generation endpoint.

How It Works

  • Create and save an endpoint in the plugin Endpoints tab.
  • Choose that saved endpoint in a workflow using the Call Endpoint step.
  • Resolve workflow variables into the endpoint URL, headers, body, and response path.
  • Send the HTTP request from the plugin.
  • Parse the response and optionally save the selected output into an endpoint output variable.

Best For

  • Sending page content to your own APIs
  • Calling Python or Node backend services from workflows
  • Resume rewrite, lead classification, and content-generation pipelines
  • Bridging browser automation with external systems

Important Notes

  • Saved endpoints support variable interpolation in url, headers_json, body_json, and response_path.
  • input_vars is documentation for expected workflow inputs, not a hard runtime restriction.
  • response_path is the cleanest way to save only one nested value from a JSON response.
  • Use the built-in endpoint test tool before wiring an endpoint into a production workflow.