LINE authentication

LINE authentication lets your users sign in with a LINE account (popular in Japan and other parts of Asia). Once connected, you can offer “Continue with LINE” in your WeWeb app.

What this integration supports

• Social sign in with LINE Login
• Redirect to different pages for success, error, and first-time users

Setup in the LINE Developers Console

You create a LINE Login channel and register WeWeb’s callback URL (the URL LINE sends users back to after sign in).

1. Create a LINE Login channel

1. Open the LINE Developers Console.
2. Create a provider (your organization) if you don’t have one yet.
3. Create a LINE Login channel.
4. Copy:
   • Channel ID
   • Channel secret

2. Add the callback URL

1. In your channel settings, open the LINE Login tab.
2. In Callback URL, add:
   • https://<your-domain>/api/auth/callback/line
3. Save your changes.

If you use multiple environments, add a callback URL for each environment (preview, staging, production).

3. (Optional) Request email permission

If you need the user’s email address, LINE requires additional approval for the email scope. You can apply for email permission from Basic settings under OpenID Connect.

Connect LINE in WeWeb

1. In the WeWeb editor, go to Data & API → Auth → Integrating providers.
2. Find LINE and expand it.
3. Turn on the Enable toggle.
4. Fill in:
   • Channel ID
   • Channel Secret
5. Click Save.

WeWeb stores these values as environment variables (for example PROVIDER_LINE_CLIENT_ID and PROVIDER_LINE_CLIENT_SECRET).

Test sign in

1. In Interface, add a “Continue with LINE” button.
2. Create a workflow on click and add Sign in with social provider.
3. Set:
   • Provider: line
   • Success page, Error page, And (optional) New user page
4. Preview your project and complete the LINE sign-in flow.

For what to do after sign in (roles, private pages, and access checks), see Users and roles overview →.

Common pitfalls

Callback URL mismatch

If LINE shows an error after you approve sign in, the callback URL is usually not registered correctly.

• In the LINE Developers Console, confirm you added https:///api/auth/callback/line under LINE Login → Callback URL.
• Make sure the domain matches the environment you are testing (preview vs production).

Email is missing

Even when LINE sign in works, the email address might not be returned unless email permission is approved.

• In your LINE channel, apply for email address permission under Basic settings → OpenID Connect.
• Only request email if you really need it, because it adds extra setup and approval.

Reference

WeWeb settings

Setting in WeWeb	Description	Where to find it in LINE
Channel ID	Identifies your LINE Login channel.	Channel Basic settings (Channel ID).
Channel Secret	Secret used to securely complete sign in.	Channel Basic settings (Channel secret).

FAQs

Which callback URL should I add in LINE?

Add https://<your-domain>/api/auth/callback/line. Add one callback URL per environment you use.

What provider value should I use in the workflow action?

Use line as the Provider value in the Sign in with social provider action.

Continue learning

Next, learn how to manage roles so you can control what signed-in users can see and do.

Users and roles overview →