A third-party smart chip in Google Docs depends on the application’s integration and the relevant add-on. A normal URL does not become a rich preview for every service automatically.
Check integration availability
The third-party developer must support smart chips, and you or your domain administrator must install the corresponding add-on. Use the organization’s approved installation process rather than installing an unfamiliar integration solely because a document contains its link.
If installation is restricted, ask the administrator. A product limitation or managed policy should not be treated as a reason to bypass account controls.
Convert a supported link
- Confirm the required add-on and account access.
- Paste the supported third-party URL.
- Use the offered Tab conversion or Chip control.
- Inspect the resulting preview and open the source resource.
Without the add-on, a reader may see the chip but not its additional preview information. The underlying service can also have its own access requirements.
Review data and audience
Check the resource title, preview content, and the integration’s requested permissions. Do not assume every collaborator has the same access to the third-party application.
The at-sign integration menu can also create resources through supported applications. Treat that as a separate external action, not merely a formatting change to a URL. Before using it, verify the destination and the intended effect. Inspect static exports separately, and keep important document meaning readable even when a recipient cannot use the chip’s live preview. A working integration should improve navigation without obscuring who can access or change the underlying resource.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.