Team social networks

← Help home

Humano can connect each team’s social accounts for dashboard metrics. There are two different kinds of credentials: the OAuth app keys (one per Humano deployment) and the per-team tokens created when an admin clicks Connect.

App keys (.env) — global for the whole product

You register one Meta app, one LinkedIn app, etc., as the developer of Humano. Their Client ID and Client Secret live in the server .env (or hosting secrets) and map to config/services.php for Laravel Socialite. Every team uses the same app; redirect URIs must match your APP_URL.

Per-team tokens — stored in the database

When a team admin connects Meta or LinkedIn, Humano receives access (and refresh) tokens tied to that user/page. Those values are stored per team (encrypted), not in .env. Disconnecting removes that row for the team.

Where team admins connect

Abrir Ajustes del equipo → Redes sociales → Gestionar, or go directly to:

https://wapify.me/team/<team_id>/settings/social

Replace <team_id> with the numeric ID of the team (same as in /team/<team_id>/settings).

Typical server variables (when OAuth is wired)

Exact names follow your config/services.php entries. Common Socialite examples:

APP_URL=https://humano.test

# Meta (Facebook Login / Graph) — example keys; align with services.facebook
FACEBOOK_CLIENT_ID=
FACEBOOK_CLIENT_SECRET=
FACEBOOK_REDIRECT_URI="${APP_URL}/integrations/social/facebook/callback"

# LinkedIn OpenID — example; align with services.linkedin-openid
LINKEDIN_CLIENT_ID=
LINKEDIN_CLIENT_SECRET=
LINKEDIN_REDIRECT_URI="${APP_URL}/integrations/social/linkedin-openid/callback"

Register the same redirect URLs in the Meta and LinkedIn developer consoles. Until OAuth routes are enabled in your build, the Connect buttons in Team Settings may stay disabled.

Bluesky

Public follower counts can use the Bluesky handle alone in some flows; optional app passwords are for authenticated API access. Team-specific handles or secrets are never global .env keys for all teams.

Related