Authenticate (Custom auth)

Use this action when you have your own sign-in system and you want WeWeb to treat the user as signed in.

Overview

Authenticate stores session information (like an access token) so WeWeb can use it in your app.

This is commonly used after:

• A login API call (for example your own API Endpoint or an external API)
• A successful OAuth flow handled outside of WeWeb

Add the action

1. In an Interface workflow, click + Add action.
2. Select Custom auth → Authenticate.

Configure the action

• Access Token: The token you received from your login system.
• Refresh Token: Optional token used to refresh the access token.
• Metadata: Optional extra details you want to keep with the session.
• Persist Session: If enabled, stores the session in the browser so it stays after refresh.

Common pitfalls

Tokens are empty

Make sure your login step ran successfully and you’re binding the values from the previous action result.

CONTINUE LEARNING

Learn how to call API Endpoints from the interface.

Executing from interface workflows →