WeKeKeWeKeKe
Sign InStart Trial
Docs / Platform Features / Integrations

Integrations

Provider connections and health checks.

Integrations keep WeKeKe connected to your social platforms. Each provider is tracked with a health state so you can quickly see whether automation is safe to run. Multi-account support is planned per provider where external APIs and policy terms allow.

Current + planned providers

X / Twitter, Instagram, and Facebook Messenger Temporarily Disabled - Under Maintenance
  • Bluesky (beta; app password)
  • X / Twitter (beta; OAuth)
  • Instagram (Meta OAuth; Business/Creator DMs) - temporarily disabled (under maintenance)
  • Facebook Messenger (Meta OAuth; Facebook Page inbox) - temporarily disabled (under maintenance)
  • Telegram (BYOB; bot token + webhook)
  • Discord (shared bot + OAuth user link)
  • TikTok (Login Kit + Content Posting API; production-approved)

Health states

  • Neutral: no credentials stored yet.
  • Connected: green state, sync healthy.
  • Error: credentials invalid or revoked.

Account options roadmap

  • Current state: one active account per provider in the integrations UI.
  • Planned state: additional account options per provider where technically possible.
  • Provider-level limits may require single-account behavior on some integrations.

What gets stored

  • Provider credentials stored securely with encryption at rest.
  • Account identifiers for sync and audit logs.
  • Last successful sync timestamp.

Operational tips

  • Reconnect after changing passwords or OAuth scopes.
  • Use test rules to verify connectivity before auto‑send.
  • Disconnect if you’re rotating credentials or pausing automation.

Security notes

  • Disconnect immediately if a provider reports suspicious activity.
  • Rotate credentials on a schedule and re‑connect.
  • Use least‑privilege scopes where supported.