Retired integrations
Understand integrations removed from new setup, their replacements and compatibility for existing workspaces.
The integrations below are no longer offered in the catalog or new workspace setup. Existing configurations, credentials, saved state and action execution remain supported. You do not need to delete or recreate an existing workspace.
Experimental integrations
agent-local-browser-controllocal-computer-controllocal-computer-control-agentweavz-dynamic-dashboard
For new hosted browser work, use Agent Browser. A hosted browser does not provide access to a person's local apps or browser profile. Existing local integrations retain their existing device and permission requirements.
Computation helpers
| Retired integration | Use instead |
|---|---|
data-transformer | Reshape JSON in Code Mode or Sandbox. |
datetime | Use date and time functions in code. |
hash-encode | Use encoding and hashing libraries in Sandbox. |
code | Use Code Mode for tool composition or Sandbox for standalone execution. |
sequential-thinking | Keep reasoning in your agent. Save useful notes in files or the scratchpad. |
Code Mode lets an agent compose available tools and transform intermediate results in one run. Sandbox runs code for work that needs a separate execution environment. Sandbox time has its own plan allowance.
The API and SDKs can still resolve and execute an existing retired integration. Creating a new workspace integration for a retired name returns INTEGRATION_RETIRED. Choose a supported replacement for new setup; migrate existing workflows only after checking their inputs, outputs and persistence needs.