Skip to content
Verified

External apps and embeds

Bring an app you already run into your dashboard by URL, and let Xuda read it and act on it.

An external app is any web app you already run somewhere else, connected by its URL. Xuda embeds it inside your dashboard through a same-origin proxy, so it can read what is on the page and, when the app allows it, act on your behalf. Nothing is installed on the app's own server and no credentials are stored: connecting it costs nothing and there is no droplet behind it.

Connect one

Enter the URL

A bare host or a full https:// address both work. This creates the app in a pending state, nothing is verified yet.

Xuda checks it can be reached

A backend fetch confirms the URL answers and records anything informational about how it responds. This step alone never decides whether the embed will work, only whether it exists.

Your browser confirms it actually renders

The dashboard loads the app through the proxy and reports back whether it drew on screen. This is the only step that decides the outcome, because embeddability is fundamentally something only your browser can observe.

That render-confirm branches to one of two outcomes:

Both tiers are a finished setup

view is not a failure state. An app that cannot be proxied still connects, in read-only mode. Only an app your browser cannot show at all fails setup, and Xuda discards the pending connection rather than leaving a broken one behind.

Once it is connected

The connected app is a standalone project in your workspace, opened through the same-origin proxy so it renders inside your dashboard. Two things happen with it:

  • Scan walks the page's DOM and returns emails, phone numbers, form fields and tables it found, each with a selector, never a screenshot.
  • Classify reads that scan and proposes suggestions in plain language, for example detecting a supplier's details and offering to file them as a contact or send a follow-up email. A suggestion either calls an ordinary Xuda method (add a contact, send an email) or drives the embedded app directly (click, fill, navigate).
Destructive actions are never automatic

A suggestion that would send, pay, delete or submit something inside the embedded app is held behind the same confirm-before-destructive gate as any other destructive action in Xuda. Nothing acts on your behalf without that confirmation, and the server enforces it independently of what the dashboard sends.

Session mode

Each connection chooses ephemeral or persist. Ephemeral drops the embedded app's login the moment you close the tab or browser, so you sign in again next time. Persist keeps it signed in. Changing it later is a non-destructive edit; it does not disturb whether the app is verified.

Changing the URL later

Repointing a connection at a different address invalidates its verification: the connection returns to pending and the render-confirm step runs again before it is trusted as active. Changing only the session mode does not.

Next