Connection Tools

Overview

Some extensions adapt to the system you connect. For example, a CRM can expose create, update, and delete tools for the standard and custom objects in your own workspace. Scrydon discovers these tools from each connection instead of showing a separate toolkit for every object.

Open an installed extension and select its Tools tab to view the available tools, their connections, and the time of each connection's last discovery.

Browse a publisher's tools

1. Open Settings → Extensions.
2. Click the extension row to open the extension sheet.
3. Select the Tools tab.

The Tools tab shows all discovered tools across every connection for that publisher. Use the search field to filter by tool name, description, or object group. Use the connection filter to focus on a specific connection.

Direct link. You can deep-link to the Tools tab by appending ?extension=<slug>&tab=tools to the Extensions page URL, for example ?extension=twenty&tab=tools.

Per-connection refresh

Within the Tools tab, each connection row shows the number of admitted tools and the time since the last successful discovery. Select Refresh on a connection to trigger immediate discovery for that connection only. Discovery reads the selected connection; it does not reuse tools from another connection.

A freshness dot on the tools count in the Installed list turns amber when the last successful sync is older than the extension's configured refresh interval.

Automatic activation for installed extensions

An installed extension automatically activates every executor that the extension explicitly declares for dynamic discovery, including write and delete executors. There are no separate executor checkboxes for extension extensions.

Installing a signed extension—or explicitly accepting the warning for an unsigned extension—delegates this executor choice to the extension and your organization's extension review process. Acceptance does not mean unsigned code was reviewed by Scrydon. Normal execution confirmation, sandboxing, egress policy, DLP, and audit controls still apply.

For a dynamic extension that was not installed from a extension, an organization admin must still choose and activate the permitted executors in the Tools tab's per-connection panel.

Discovery and refresh

Scrydon attempts discovery after activation and relevant connection or extension-version changes. It also refreshes a never-synced or stale connection when an admin opens the Tools tab for that connection. These refreshes are best effort: a connection can be saved even if discovery is temporarily unavailable.

To refresh immediately, select Refresh on the connection row in the Tools tab.

If a refresh fails, Scrydon displays a retryable error and keeps the last successfully synced tools available. A successful later refresh replaces the connection's discovered set, including removing tools for objects that no longer exist.

Connect flow

When you connect a new account for a dynamic extension, the connection flow includes a discovery step. Scrydon attempts an initial discovery immediately after the connection is saved. The result — admitted tool count or an error — appears before you close the connect dialog. You can also trigger a Refresh from the Tools tab later.

Tool status and diagnostics

Only admitted tools are available to agents. Expand Diagnostics when it appears:

• Withheld means the descriptor uses an executor outside the active grant. For an installed extension, verify that the installed code artifact declares that executor and refresh again. Manually configured extensions can let an admin permit it.
• Rejected means the descriptor failed a non-overridable admission control, such as malformed structure or an attempt to bind credentials, headers, URLs, or a connection selector. Contact the extension publisher with the displayed reason.
• Limited means the connection reached its configured or platform tool limit, or some descriptors were withheld or rejected.

The discovery tool and its generic create/update/delete executors are internal plumbing. Agents see the useful discovered actions, not those infrastructure tools.

Tools that cannot be admitted are listed under Unavailable at the bottom of the connection's tool list.

Stop using connection tools

For an installed extension, disable or delete the connection to remove its live tool grant. Historical grant and audit records remain available for governance evidence. A manually configured extension also exposes a manual action in its Tools tab.

In-flight executions are not interrupted when a connection is disabled.

Troubleshooting

The Tools tab shows no tools for a connection.

• Make sure the connection is enabled and configured.
• Activate a workspace environment, then select Refresh.
• Confirm that the connected account can inspect the extension's object schema.

A refresh reports an internal or transport error.

• Retry with Refresh. Previously synced tools remain available.
• If the error persists, share the connection name and sync time with your Scrydon administrator; do not include credentials.

Expected objects are missing.

• Confirm that the connected account can read those objects in the source system.
• Clear the search field and check Unavailable and the tool-limit notice.
• Run Refresh after changing the source system's schema.

Tools from one workspace appear under another.

• Close the extension sheet and reopen the Tools tab, then use the connection filter to select the intended connection. If the catalog still appears incorrect, report both connection names; discovery and storage are designed to be connection-scoped.