BrowserAct for Dify
Run BrowserAct Bots and official templates from a Dify workflow, and wait for
the result inside the node.
BrowserAct is a hosted browser-automation service. You build or choose a Bot in
BrowserAct, then this plugin starts a task with your inputs and returns the task
result as JSON.
Tools
Both tools share the same connection, parameters and output shape.
Requirements
- Dify Community Edition or Dify Cloud.
- A BrowserAct account with at least one published Bot, or access to official
templates.
- A BrowserAct API Key. Visit the BrowserAct website to get your API Key.
- Outbound HTTPS access to . The host is fixed; the plugin
does not accept a custom endpoint.
Install
- Install BrowserAct from the Dify Marketplace, or upload the
file from the Plugins page.
- Open Plugins → BrowserAct → Authorize and paste your BrowserAct API Key.
- Add a Run My Bot or Run Official Template node to a workflow.
The API Key is stored by Dify as the Provider credential and sent to BrowserAct
as a Bearer token. Saving the credential validates it against your Bot list; it
does not start a task.
Configure a node
Find the right input parameters
- Set Operation to and run the node.
- Open LAST RUN and copy the full output.
- Paste it into Custom Parameters JSON and edit the values inside .
- Switch Operation back to or .
lists every field in . Explicit
defaults are preserved. Fields without defaults use editable placeholders:
strings , numbers , booleans , arrays , and objects .
Nullable types use the first declared non-null type; fields without a known
type use . Fill in the placeholders before running; they may not meet
constraints such as minimum length or allowed values. Omit optional fields you
do not want to send. The run mode only fills explicit defaults automatically.
Objects merge recursively and arrays are replaced. Explicit , and
empty strings are kept. Inputs are validated against the Bot's input schema
before the task is created.
Output
The node returns the complete task detail as one JSON message, plus named
variables for downstream nodes:
, , , , , ,
, , , , ,
, , , ,
, .
Notes:
- and are strings, so large numeric IDs keep their digits.
- keeps the Bot's original JSON type. Bots do not share a fixed result
schema, so typed pickers may show it as unknown; select the complete
variable or use a Code node when you need a specific type.
- is keyed by format (, , , , ).
Each entry has a temporary download URL. Inline results are limited to 5 MB;
generated files are limited to 100 MB each.
- File URLs are temporary. Use them before ; the plugin does
not download, re-upload or extend them.
Waiting, timeout and errors
- The wait starts when the task is created and defaults to 600 seconds.
- On timeout the node fails and keeps . The plugin stops polling but
does not cancel the remote task; BrowserAct may cancel it later according to
its own heartbeat and scheduling policy.
- A or task ends the wait immediately and is reported as a
failure with the current state and . Paused tasks are not resumed
automatically.
- and tasks report the failure information returned by the
API.
- Task creation is never retried automatically, so an unclear response cannot
create a duplicate task.
- HTTP requests use a 30-second inactivity timeout, clamped to the remaining
wait budget.
Limitations
- A node runs one task and waits for it; long tasks can exceed the single-step
timeout of the Dify editor even though the task keeps running in the
background.
- Large outputs may not stream to the editor reliably. Check the run history
before retrying.
- The task result is not converted or reshaped. Downstream typing depends on
the Bot's own output.
- A disconnected browser page does not stop the plugin from polling, and does
not prove that polling stopped.
Data and privacy
The plugin sends your API Key and task inputs to BrowserAct and returns task
results to Dify. It keeps a small in-memory cache of list options for 60 seconds
and writes nothing to disk. See PRIVACY.md for the full data flow.
Documentation
Source and support