Connected accounts

Connected accounts are in beta. Some websites may have trouble connecting or staying signed in. They let a private API use a website account without putting its password or session tokens in the generated workflow.

Connect an account#

An organization owner or admin opens Connections & keys → Connected accounts in Studio and enters a website URL. Live progress starts immediately while Fous discovers the website’s sign-in page. Studio shows the site icon, discovered sign-in URL, and the fields needed to continue. There is no integration catalog or Fous administrator approval.

Enter the requested details. Fous handles the website in the background and presents any additional fields, such as a verification code, in the same interface. Fous verifies the account and workspace, tests the session in a fresh browser, and saves the connection automatically. Choose Reconnect to start a fresh sign-in for a saved website immediately. Fous uses the account you sign in to for the renewed connection.

The agent sees private placeholders in place of your sign-in details. Trusted tools fill the original website fields. Fous preserves the authorized session encrypted. The URL-based flow saves your session without retaining your password. A site may still require you to return for a new verification or approval step. If its required device or browser challenge cannot be completed through this interface, Fous explains the limitation and leaves the account unconnected.

Build a private API#

Select the account in the build settings before starting. APIs with connected accounts remain private. When extending an API, its account bindings are inherited; you can replace or remove a binding in the settings.

If an account needs a fresh sign-in before a build starts, Studio opens a sign-in dialog and takes you to Connected accounts. Returning to the workflow keeps your draft. If a session needs attention during a build, the saved build waits for reconnection and resumes from saved progress once the required accounts are ready.

Calls and actions#

Calls use the account and workspace approved for that connection. Fous checks that the connection and published API version remain available. Connected results are not cached.

Verification does not execute business actions. Some integrations provide explicitly labelled fixtures to test code after an action would return a result. Those fixtures do not prove that a real action ran.

When a source action's response is lost, the action may already have completed. Inspect the destination and resolve the uncertain outcome before starting a new request. Reconnecting an account does not replay previous actions. See request replay for request idempotency and saved responses.

Revoke access#

An admin can revoke an account from Connections & keys → Connected accounts. New calls using that connection stop, and Fous deletes the saved session. Remote profiles, when present, are queued for cleanup. If the source provides its own access-management page, you can also revoke Fous there. Revocation does not undo an action the source already accepted.